Context-specific user interfaces

ABSTRACT

Context-specific user interfaces for use with a portable multifunction device are disclosed. The methods described herein for context-specific user interfaces provide indications of time and, optionally, a variety of additional information. Further disclosed are non-transitory computer-readable storage media, systems, and devices configured to perform the methods described herein.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/815,879, filed Jul. 31, 2015, which is a continuation ofInternational Patent Application Serial No. PCT/US2015/034604, filedJun. 7, 2015, which claims priority to the following applications: U.S.Provisional Patent Application Ser. No. 62/032,562, filed Aug. 2, 2014;U.S. Provisional Patent Application Ser. No. 62/044,994, filed Sep. 2,2014; U.S. Provisional Patent Application Ser. No. 62/129,835, filedMar. 7, 2015. All of these applications are hereby incorporated byreference in their entirety.

This application relates to the following applications: InternationalPatent Application Serial No. PCT/US2013/040087, entitled “Device,Method, and Graphical User Interface for Moving a User Interface ObjectBased on an Intensity of a Press Input,” filed May 8, 2013;International Patent Application Serial No. PCT/US2013/040072, entitled“Device, Method, and Graphical User Interface for Providing Feedback forChanging Activation States of a User Interface Object,” filed May 8,2013; International Patent Application Serial No. PCT/US2013/040070,entitled “Device, Method, and Graphical User Interface for ProvidingTactile Feedback for Operations Performed in a User Interface,” filedMay 8, 2013; International Patent Application Serial No.PCT/US2013/040067, entitled “Device, Method, and Graphical UserInterface for Facilitating User Interaction with Controls in a UserInterface,” filed May 8, 2013; International Patent Application SerialNo. PCT/US2013/040061, entitled “Device, Method, and Graphical UserInterface for Displaying User Interface Objects Corresponding to anApplication,” filed May 8, 2013; International Patent Application SerialNo. PCT/US2013/040058, entitled “Device, Method, and Graphical UserInterface for Displaying Additional Information in Response to a UserContact,” filed May 8, 2013; International Patent Application Serial No.PCT/US2013/040056, entitled “Device, Method, and Graphical UserInterface for Scrolling Nested Regions,” filed May 8, 2013;International Patent Application Serial No. PCT/US2013/040054, entitled“Device, Method, and Graphical User Interface for Manipulating FramedGraphical Objects,” filed May 8, 2013; International Patent ApplicationSerial No. PCT/US2013/069489, entitled “Device, Method, and GraphicalUser Interface for Switching Between User Interfaces,” filed Nov. 11,2013; International Patent Application Serial No. PCT/US2013/069486,entitled “Device, Method, and Graphical User Interface for DeterminingWhether to Scroll or Select Content,” filed Nov. 11, 2013; InternationalPatent Application Serial No. PCT/US2013/069484, entitled “Device,Method, and Graphical User Interface for Moving a Cursor According to aChange in an Appearance of a Control Icon with SimulatedThree-Dimensional Characteristics,” filed Nov. 11, 2013; InternationalPatent Application Serial No. PCT/US2013/069483, entitled “Device,Method, and Graphical User Interface for Transitioning Between TouchInput to Display Output Relationships,” filed Nov. 11, 2013;International Patent Application Serial No. PCT/US2013/069479, entitled“Device, Method, and Graphical User Interface for Forgoing Generation ofTactile Output for a Multi-Contact Gesture,” filed Nov. 11, 2013;International Patent Application Serial No. PCT/US2013/069472, entitled“Device, Method, and Graphical User Interface for Navigating UserInterface Hierarchies,” filed Nov. 11, 2013; International PatentApplication Serial No. PCT/US2013/040108, entitled “Device, Method, andGraphical User Interface for Moving and Dropping a User InterfaceObject,” filed May 8, 2013; International Patent Application Serial No.PCT/US2013/040101, entitled “Device, Method, and Graphical UserInterface for Selecting User Interface Objects,” filed May 8, 2013;International Patent Application Serial No. PCT/US2013/040098, entitled“Device, Method, and Graphical User Interface for Displaying ContentAssociated with a Corresponding Affordance,” filed May 8, 2013;International Patent Application Serial No. PCT/US2013/040093, entitled“Device, Method, and Graphical User Interface for Transitioning BetweenDisplay States in Response to a Gesture,” filed May 8, 2013;International Patent Application Serial No. PCT/US2013/040053, entitled“Device, Method, and Graphical User Interface for Selecting Objectwithin a Group of Objects,” filed May 8, 2013; U.S. Patent ApplicationSer. No. 61/778,211, entitled “Device, Method, and Graphical UserInterface for Facilitating User Interaction with Controls in a UserInterface,” filed Mar. 12, 2013; U.S. Patent Application Ser. No.61/778,191, entitled “Device, Method, and Graphical User Interface forDisplaying User Interface Objects Corresponding to an Application,”filed Mar. 12, 2013; U.S. Patent Application Ser. No. 61/778,171,entitled “Device, Method, and Graphical User Interface for DisplayingAdditional Information in Response to a User Contact,” filed Mar. 12,2013; U.S. Patent Application Ser. No. 61/778,179, entitled “Device,Method and Graphical User Interface for Scrolling Nested Regions,” filedMar. 12, 2013; U.S. Patent Application Ser. No. 61/778,156, entitled“Device, Method, and Graphical User Interface for Manipulating FramedGraphical Objects,” filed Mar. 12, 2013; U.S. Patent Application Ser.No. 61/778,125, entitled “Device, Method, And Graphical User Interfacefor Navigating User Interface Hierarchies,” filed Mar. 12, 2013; U.S.Patent Application Ser. No. 61/778,092, entitled “Device, Method, andGraphical User Interface for Selecting Object Within a Group ofObjects,” filed Mar. 12, 2013; U.S. Patent Application Ser. No.61/778,418, entitled “Device, Method, and Graphical User Interface forSwitching Between User Interfaces,” filed Mar. 13, 2013; U.S. PatentApplication Ser. No. 61/778,416, entitled “Device, Method, and GraphicalUser Interface for Determining Whether to Scroll or Select Content,”filed Mar. 13, 2013; U.S. Patent Application Ser. No. 61/747,278,entitled “Device, Method, and Graphical User Interface for ManipulatingUser Interface Objects with Visual and/or Haptic Feedback,” filed Dec.29, 2012; U.S. Patent Application Ser. No. 61/778,414, entitled “Device,Method, and Graphical User Interface for Moving and Dropping a UserInterface Object,” filed Mar. 13, 2013; U.S. Patent Application Ser. No.61/778,413, entitled “Device, Method, and Graphical User Interface forSelecting User Interface Objects,” filed Mar. 13, 2013; U.S. PatentApplication Ser. No. 61/778,412, entitled “Device, Method, and GraphicalUser Interface for Displaying Content Associated with a CorrespondingAffordance,” filed Mar. 13, 2013; U.S. Patent Application Ser. No.61/778,373, entitled “Device, Method, and Graphical User Interface forManaging Activation of a Control Based on Contact Intensity,” filed Mar.12, 2013; U.S. Patent Application Ser. No. 61/778,265, entitled “Device,Method, and Graphical User Interface for Transitioning Between DisplayStates in Response to a Gesture,” filed Mar. 12, 2013; U.S. PatentApplication Ser. No. 61/778,367, entitled “Device, Method, and GraphicalUser Interface for Moving a User Interface Object Based on an Intensityof a Press Input,” filed Mar. 12, 2013; U.S. Patent Application Ser. No.61/778,363, entitled “Device, Method, and Graphical User Interface forTransitioning Between Touch Input to Display Output Relationships,”filed Mar. 12, 2013; U.S. Patent Application Ser. No. 61/778,287,entitled “Device, Method, and Graphical User Interface for ProvidingFeedback for Changing Activation States of a User Interface Object,”filed Mar. 12, 2013; U.S. Patent Application Ser. No. 61/778,284,entitled “Device, Method, and Graphical User Interface for ProvidingTactile Feedback for Operations Performed in a User Interface,” filedMar. 12, 2013; U.S. Patent Application Ser. No. 61/778,239, entitled“Device, Method, and Graphical User Interface for Forgoing Generation ofTactile Output for a Multi-Contact Gesture,” filed Mar. 12, 2013; U.S.Patent Application Ser. No. 61/688,227, entitled “Device, Method, andGraphical User Interface for Manipulating User Interface Objects withVisual and/or Haptic Feedback,” filed May 9, 2012; U.S. ProvisionalPatent Application Ser. No. 61/645,033, filed on May 9, 2012, entitled“Adaptive Haptic Feedback for Electronic Devices;” U.S. ProvisionalPatent Application Ser. No. 61/665,603, filed on Jun. 28, 2012, entitled“Adaptive Haptic Feedback for Electronic Devices;” and U.S. ProvisionalPatent Application Ser. No. 61/681,098, filed on Aug. 8, 2012, entitled“Adaptive Haptic Feedback for Electronic Devices;” U.S. ProvisionalPatent Application Ser. No. 62/044,894, filed on Sep. 2, 2014, entitled“Reduced-Size Interfaces for Managing Alerts;” U.S. Provisional PatentApplication Ser. No. 62/044,979, filed on Sep. 2, 2014, entitled“Stopwatch and Timer User Interfaces;” U.S. Provisional PatentApplication Ser. No. 62/026,532, “Raise Gesture Detection in a Device,”filed Jul. 18, 2014; and U.S. patent application Ser. No. 14/476,700,“Crown Input for a Wearable Electronic Device,” filed Sep. 3, 2014. Thecontent of these applications is hereby incorporated by reference intheir entirety.

FIELD

The present disclosure relates generally to computer user interfaces,and more specifically to context-specific user interfaces for indicatingtime.

BACKGROUND

Users rely on portable multifunction devices for keeping time, among avariety of other operations including running software applications. Itis desirable to allow the user to access information through a singleuser interface while keeping the interface simple and intuitive to use.Further, a user may want to access different types of information, suchas various aspects related to keeping time, or different applicationdata points, in different contexts. It is therefore also desirable toallow the user to customize the user interface and the types ofinformation provided through the user interface.

SUMMARY

Portable multifunction devices are able to provide many different typesof information and interfaces to a user, and a user may wish tocustomize these user interfaces, and the types of information theyprovide, in different contexts. Therefore, context-specific userinterfaces for keeping time are increasingly desirable.

Some techniques for managing (e.g., editing) context-specific userinterfaces for indicating time using electronic devices, however, aregenerally cumbersome and inefficient. For example, existing techniquesuse a complex and time-consuming user interface, which may includemultiple key presses or keystrokes. Existing techniques require moretime than necessary, wasting user time and device energy. This latterconsideration is particularly important in battery-operated devices.

Accordingly, the present invention provides, inter alia, the benefit ofportable electronic devices with faster, more efficient methods andinterfaces for managing context-specific user interfaces. Such methodsand interfaces optionally complement or replace other methods formanaging context-specific user interfaces. Such methods and interfacesreduce the cognitive burden on a user and produce a more efficienthuman-machine interface. Such methods and interfaces may also reduce thenumber of unnecessary, extraneous, repetitive, and/or redundant inputs,and may create a faster and more efficient user interface arrangement,which may reduce the number of required inputs, reduce processing power,and reduce the amount of time for which user interfaces need to bedisplayed in order for desired functions to be accessed and carried out.For battery-operated computing devices, such methods and interfacesconserve power and increase the time between battery charges.

The above deficiencies and other problems are reduced or eliminated bythe disclosed devices, methods, and computer-readable media. In someembodiments, the device is a desktop computer. In some embodiments, thedevice is portable (e.g., a notebook computer, tablet computer, orhandheld device). In some embodiments, the device has a touchpad. Insome embodiments, the device has a touch-sensitive display (also knownas a “touch screen” or “touch screen display”). In some embodiments, thedevice has hardware input mechanisms such as depressible buttons and/orrotatable input mechanisms. In some embodiments, the device has agraphical user interface (GUI), one or more processors, memory, and oneor more modules, programs, or sets of instructions stored in the memoryfor performing multiple functions. In some embodiments, the userinteracts with the GUI through finger contacts and gestures on thetouch-sensitive surface and/or through rotating the rotatable inputmechanism and/or through depressing hardware buttons. In someembodiments, the functions optionally include image editing, drawing,presenting, word processing, website creating, disk authoring,spreadsheet making, game playing, telephoning, video conferencing,e-mailing, instant messaging, workout support, digital photographing,digital videoing, web browsing, digital music playing, and/or digitalvideo playing. Executable instructions for performing these functionsare, optionally, included in a non-transitory computer-readable storagemedium or other computer program product configured for execution by oneor more processors. Executable instructions for performing thesefunctions are, optionally, included in a transitory computer-readablestorage medium or other computer program product configured forexecution by one or more processors.

In some embodiments, a method of providing context-specific userinterfaces comprises: at an electronic device with a display: receivingdata representing a user input, and in response to receiving the data:displaying a user interface screen on the display, the user interfacescreen including a clock face indicating a first time, wherein the firsttime precedes a current time; and updating the user interface screen byanimating the clock face to transition from indicating the first time toindicating the current time, wherein the animation represents thepassage of time from the first time to the current time.

In some embodiments, a method of providing context-specific userinterfaces comprises: at an electronic device with a touch-sensitivedisplay: displaying on the touch-sensitive display a clock face thatindicates current time, the clock face including: a user interfaceobject comprising an hour hand and a minute hand, wherein the userinterface object indicates the current time; one or more indications ofan hourly timescale; and a stopwatch hand; receiving data representing auser input; and in response to receiving the data: substituting the oneor more indications of an hourly timescale with an indication of a firsttimescale for the stopwatch hand; and animating the stopwatch hand toreflect passage of time.

In some embodiments, a method of providing context-specific userinterfaces comprises: at an electronic device with a touch-sensitivedisplay: displaying on the touch-sensitive display a user interfacescreen, the user interface screen including: a first affordancerepresenting a simulation of a first region of the Earth as illuminatedby the Sun at a current time; and a second affordance indicating thecurrent time; receiving a user input; and in response to receiving theuser input: rotating the simulation of the Earth to display a secondregion of the Earth as illuminated by the Sun at the current time.

In some embodiments, a method of providing context-specific userinterfaces comprises: at an electronic device with a touch-sensitivedisplay: displaying on the touch-sensitive display a user interfacescreen, the user interface screen comprising: a first portion of theuser interface screen, the first portion indicating daytime; a secondportion of the user interface screen, the second portion indicatingnighttime; a user interface object, the user interface objectrepresenting a sinusoidal wave with a period representing a day, whereinthe sinusoidal wave indicates a path of the Sun through the day, andwherein the sinusoidal wave is displayed in one or more of the firstportion and the second portion; a first affordance representing the Sun,wherein the first affordance is displayed at a first position on thedisplayed sinusoidal wave, the first position indicating a current timeof the day and whether the current time of the day is during daytime ornighttime; and a second affordance, the second affordance indicating thecurrent time of day.

In some embodiments, a method of providing context-specific userinterfaces comprises: at an electronic device with a touch-sensitivedisplay: displaying a user interface screen on the display, the userinterface screen including: a background based on an image, thebackground comprising a plurality of pixels, wherein a subset of thepixels are modified in appearance relative to the image such that thesubset of pixels represents one or more of: a first user interfaceobject indicating a date; and a second user interface object indicatinga time of day.

In some embodiments, a method of providing context-specific userinterfaces comprises: at an electronic device with a display: accessinga folder, the folder including two or more images; selecting from thefolder a first image; and displaying on the display a user interfacescreen, the user interface screen comprising: a background based on thefirst image, the background comprising a plurality of pixels, wherein asubset of the pixels are modified in appearance relative to the imagesuch that the subset of pixels represents one or more of: a first userinterface object indicating a date; and a second user interface objectindicating a time of day.

In some embodiments, a method of providing context-specific userinterfaces comprises: at an electronic device with a touch-sensitivedisplay: detecting a user input, wherein the user input is detected at afirst time, and in response to detecting the user input: displaying auser interface screen, the user interface screen including: a first userinterface object indicating the first time; and a second user interfaceobject; and animating the second user interface object, the animationcomprising a sequential display of a first animated sequence, a secondanimated sequence after the first animated sequence, and a thirdanimated sequence after the second animated sequence, wherein the firstanimated sequence, the second animated sequence, and the third animatedsequence are different; after animating the second user interfaceobject, detecting a second user input, wherein the second user input isdetected at a second time, wherein the second time is after the firsttime, and in response to detecting the second user input: accessing datarepresenting the previously displayed second animated sequence;selecting a fourth animated sequence, wherein the fourth animatedsequence is different from the first animated sequence and the secondanimated sequence; displaying a second user interface screen, the seconduser interface screen including: the first user interface object,wherein the first user interface object is updated to indicate thesecond time; and a third user interface object related to the seconduser interface object; and animating the third user interface object,the animation comprising a sequential display of the first animatedsequence, the fourth animated sequence after the first animatedsequence, and the third animated sequence after the fourth animatedsequence.

In some embodiments, a method of providing context-specific userinterfaces comprises: at an electronic device with a touch-sensitivedisplay: detecting a user movement of the electronic device; and, inresponse to detecting the movement: displaying an animated reveal of aclock face, wherein the animation comprises: displaying an hour hand anda minute hand; and displaying a first hour indication; and afterdisplaying the first hour indication, displaying a second hourindication, wherein the second hour indication is displayed on the clockface at a position after the first hour indication in a clockwisedirection.

In some embodiments, a method of indicating time with a character-baseduser interface comprises: at an electronic device with a display and atouch-sensitive surface: displaying a character user interface object onthe display, the character user interface object comprisingrepresentations of a first limb and a second limb, wherein the characteruser interface object indicates a first time by: indicating a first hourwith the first limb and a first minute with the second limb; andupdating the character user interface object to indicate a second time,wherein the character indicates the second time by: indicating a secondhour with the second limb and a second minute with the first limb.

In some embodiments, a method of indicating time with a character-baseduser interface comprises: at an electronic device with a display and atouch-sensitive surface: displaying a character user interface object onthe display, the character user interface object comprising arepresentation of a limb, the limb including: a first endpoint of thelimb having a first position, wherein the first endpoint of the limb isan axis of rotation for the limb, and a second endpoint of the limbhaving a second position, wherein the position of the second endpoint ofthe limb indicates a first time value; and updating the character userinterface object to indicate a second time value, wherein updating thecharacter user interface object comprises moving the first endpoint ofthe limb to a third position, and moving the second endpoint of the limbto a fourth position to indicate the second time value.

In some embodiments, a method of indicating time with a character-baseduser interface comprises: at an electronic device with a display and atouch-sensitive surface: displaying a character user interface object onthe display, the character user interface object comprising arepresentation of a limb, the limb including a first segment of the limband a second segment of the limb, wherein the first segment of the limbconnects a first endpoint of the limb to a joint of the limb, the firstendpoint of the limb having a first position, and wherein the secondsegment of the limb connects a second endpoint of the limb to the jointof the limb, the second endpoint of the limb having a second position,wherein the joint of the limb is an axis of rotation for the secondsegment of the limb, and wherein the position of the second endpoint ofthe limb indicates a first time value, and updating the character userinterface object to indicate a second time value, wherein updatingcomprises moving the second endpoint of the limb along the axis ofrotation for the second segment of the limb to a third position toindicate the second time.

In some embodiments, a method of indicating time with a character-baseduser interface comprises: at an electronic device with a display and atouch-sensitive surface: displaying a character user interface object onthe display, wherein the character user interface object indicates time;receiving first data indicative of an event; determining whether theevent meets a condition; and in accordance with the determination thatthe event meets the condition: updating the displayed character userinterface object by changing a visual aspect of the character userinterface object.

In some embodiments, a method of indicating time with a character-baseduser interface comprises: at an electronic device with a display and atouch-sensitive surface: setting the display to an inactive state;receiving first data indicative of an event; in response to receivingthe first data: setting the display to an active state; displaying acharacter user interface object on a side of the display; animating thecharacter user interface object towards a center of the display; anddisplaying the character user interface at the center of the display ina position that indicates a current time.

In some embodiments, a method of providing context-specific userinterfaces comprises: at an electronic device with a touch-sensitivedisplay: a clock face; and an affordance wherein the affordancerepresents an application, wherein the affordance comprises a set ofinformation obtained from the application, wherein the set ofinformation is updated in accordance with data from the application, andwherein the affordance is displayed as a complication on the clock face;detecting a contact on the displayed affordance, and in response todetecting the contact: launching the application represented by theaffordance.

In some embodiments, a method of providing context-specific userinterfaces comprises: at an electronic device with a touch-sensitivedisplay configured to detect intensity of contacts: displaying on thetouch-sensitive display a user interface screen including a clock face;detecting a contact on the touch-sensitive display, the contact having acharacteristic intensity, and in response to detecting the contact:determining whether the characteristic intensity is above an intensitythreshold; and in accordance with a determination that thecharacteristic intensity is above the intensity threshold: entering aclock face edit mode of the electronic device; visually distinguishingthe displayed clock face to indicate the clock face edit mode; anddetecting a second contact on the touch-sensitive display, wherein thesecond contact is on the visually distinguished displayed clock face,and in response to detecting the second contact: visually indicating anelement of the clock face for editing.

In some embodiments, a method of providing context-specific userinterfaces comprises: at an electronic device with a touch-sensitivedisplay configured to detect intensity of contacts: displaying on thetouch-sensitive display a user interface screen including a clock face;detecting a contact on the touch-sensitive display, the contact having acharacteristic intensity, and in response to detecting the contact:determining whether the characteristic intensity is above an intensitythreshold; and in accordance with a determination that thecharacteristic intensity is above the intensity threshold: entering aclock face selection mode of the electronic device; visuallydistinguishing the displayed clock face to indicate the clock faceselection mode, wherein the displayed clock face is centered on thedisplay; and detecting a swipe on the touch-sensitive display, and inresponse to detecting the swipe: centering a second clock face on thedisplay.

In some embodiments, a method of providing context-specific userinterfaces comprises: at an electronic device with a touch-sensitivedisplay and a rotatable input mechanism: displaying on thetouch-sensitive display a user interface screen, the user interfacescreen including: a clock face; and an affordance on the clock face, theaffordance indicating a first time of day; detecting a contact on thetouch-sensitive display; and in response to detecting the contact:entering a user interaction mode of the electronic device; while theelectronic device is in the user interaction mode, detecting a movementof the rotatable input mechanism, and in response to detecting themovement: updating the affordance to indicate a second time of day;detecting a second contact on the touch-sensitive display at theaffordance indicating the second time, and in response to detecting thesecond contact: setting a user reminder for the second time of day.

In some embodiments, a method of providing context-specific userinterfaces comprises: at an electronic device with a touch-sensitivedisplay: displaying on the display a user interface screen, the userinterface screen including a plurality of affordances, the pluralityincluding a first affordance, wherein the first affordance indicates aclock face that includes: an indication of time; and an outline;detecting a contact on the displayed first affordance; and in responseto detecting the contact: substituting the display of the user interfacescreen with a second user interface screen, wherein the substitutioncomprises retaining one of the one or more of the indication of time andthe outline, wherein the retained indication of time or outline isdisplayed on the second user interface screen at a size larger than onthe first user interface screen.

In some embodiments, a device comprises means for receiving datarepresenting a user input; means responsive to receiving the data fordisplaying a user interface screen on a display, the user interfacescreen including a clock face indicating a first time, wherein the firsttime precedes a current time; and means for updating the user interfacescreen by animating the clock face to transition from indicating thefirst time to indicating the current time, wherein the animationrepresents the passage of time from the first time to the current time.

In some embodiments, a device comprises means for displaying a clockface on a touch-sensitive display that indicates current time, the clockface including: a user interface object comprising an hour hand and aminute hand, wherein the user interface object indicates the currenttime; one or more indications of an hourly timescale; and a stopwatchhand; means for receiving data representing a user input; meansresponsive to receiving the data for substituting the one or moreindications of an hourly timescale with an indication of a firsttimescale for the stopwatch hand; and means for animating the stopwatchhand to reflect passage of time.

In some embodiments, a device comprises means for displaying on atouch-sensitive display a user interface screen, the user interfacescreen including: a first affordance representing a simulation of afirst region of the Earth as illuminated by the Sun at a current time;and a second affordance indicating the current time; means for receivinga user input; and means responsive to receiving the user input forrotating the simulation of the Earth to display a second region of theEarth as illuminated by the Sun at the current time.

In some embodiments, a device comprises means for displaying on atouch-sensitive display a user interface screen, the user interfacescreen comprising: a first portion of the user interface screen, thefirst portion indicating daytime; a second portion of the user interfacescreen, the second portion indicating nighttime; a user interfaceobject, the user interface object representing a sinusoidal wave with aperiod representing a day, wherein the sinusoidal wave indicates a pathof the Sun through the day, and wherein the sinusoidal wave is displayedin one or more of the first portion and the second portion; a firstaffordance representing the Sun, wherein the first affordance isdisplayed at a first position on the displayed sinusoidal wave, thefirst position indicating a current time of the day and whether thecurrent time of the day is during daytime or nighttime; and a secondaffordance, the second affordance indicating the current time of day.

In some embodiments, a device comprises means for displaying a userinterface screen on a display, the user interface screen including: abackground based on an image, the background comprising a plurality ofpixels, wherein a subset of the pixels are modified in appearancerelative to the image such that the subset of pixels represents one ormore of: a first user interface object indicating a date; and a seconduser interface object indicating a time of day.

In some embodiments, a device comprises means for accessing a folder,the folder including two or more images; means for selecting from thefolder a first image; and means for displaying on a display a userinterface screen, the user interface screen comprising: a backgroundbased on the first image, the background comprising a plurality ofpixels, wherein a subset of the pixels are modified in appearancerelative to the image such that the subset of pixels represents one ormore of: a first user interface object indicating a date; and a seconduser interface object indicating a time of day.

In some embodiments, a device comprises means for detecting a userinput, wherein the user input is detected at a first time; meansresponsive to detecting the user input for displaying a user interfacescreen, the user interface screen including: a first user interfaceobject indicating the first time; and a second user interface object;means for animating the second user interface object, the animationcomprising a sequential display of a first animated sequence, a secondanimated sequence after the first animated sequence, and a thirdanimated sequence after the second animated sequence, wherein the firstanimated sequence, the second animated sequence, and the third animatedsequence are different; means for detecting a second user input, whereinthe second user input is detected at a second time, wherein the secondtime is after the first time; means responsive to detecting the seconduser input for accessing data representing the previously displayedsecond animated sequence; means for selecting a fourth animatedsequence, wherein the fourth animated sequence is different from thefirst animated sequence and the second animated sequence; means fordisplaying a second user interface screen, the second user interfacescreen including: the first user interface object, wherein the firstuser interface object is updated to indicate the second time; and athird user interface object related to the second user interface object;and means for animating the third user interface object, the animationcomprising a sequential display of the first animated sequence, thefourth animated sequence after the first animated sequence, and thethird animated sequence after the fourth animated sequence.

In some embodiments, a device comprises means for detecting a usermovement of the device; means responsive to detecting the user movementfor displaying an animated reveal of a clock face, wherein the animationcomprises: displaying an hour hand and a minute hand; and displaying afirst hour indication; and means for displaying a second hourindication, wherein the second hour indication is displayed on the clockface at a position after the first hour indication in a clockwisedirection.

In some embodiments, a device comprises means for displaying a userinterface screen on a display, the user interface screen including: aclock face; and an affordance wherein the affordance represents anapplication, wherein the affordance comprises a set of informationobtained from the application, wherein the set of information is updatedin accordance with data from the application, and wherein the affordanceis displayed as a complication on the clock face; means for detecting acontact on the displayed affordance; and means responsive to detectingthe contact for launching the application represented by the affordance.

In some embodiments, a device comprises means for displaying on atouch-sensitive display a user interface screen including a clock face;means for detecting a contact on the touch-sensitive display, thecontact having a characteristic intensity; means responsive to detectingthe contact for determining whether the characteristic intensity isabove an intensity threshold; means for entering a clock face edit modeof the electronic device in accordance with a determination that thecharacteristic intensity is above the intensity threshold; means forvisually distinguishing the displayed clock face to indicate the clockface edit mode; means for detecting a second contact on thetouch-sensitive display, wherein the second contact is on the visuallydistinguished displayed clock face; and means responsive to detectingthe second contact for visually indicating an element of the clock facefor editing.

In some embodiments, a device comprises means for displaying on atouch-sensitive display a user interface screen including a clock face;means for detecting a contact on the touch-sensitive display, thecontact having a characteristic intensity; means responsive to detectingthe contact for determining whether the characteristic intensity isabove an intensity threshold; means for entering a clock face selectionmode of the electronic device in accordance with a determination thatthe characteristic intensity is above the intensity threshold; means forvisually distinguishing the displayed clock face to indicate the clockface selection mode, wherein the displayed clock face is centered on thedisplay; means for detecting a swipe on the touch-sensitive display; andmeans responsive to detecting the swipe for centering a second clockface on the display.

In some embodiments, a device comprises means for displaying a userinterface screen on a touch-sensitive display, the user interface screenincluding: a clock face; and an affordance on the clock face, theaffordance indicating a first time of day; means for detecting a contacton the touch-sensitive display; means responsive to detecting thecontact for entering a user interaction mode of the electronic device;means for detecting a movement of the rotatable input mechanism whilethe device is in the user interaction mode; means responsive todetecting the movement for updating the affordance to indicate a secondtime of day; means for detecting a second contact on the touch-sensitivedisplay at the affordance indicating the second time; and meansresponsive to detecting the second contact for setting a user reminderfor the second time of day.

In some embodiments, a device comprises means for displaying a userinterface screen on a display, the user interface screen including aplurality of affordances, the plurality including a first affordance,wherein the first affordance indicates a clock face that includes: anindication of time; and an outline; means for detecting a contact on thedisplayed first affordance; and means responsive to detecting thecontact for substituting the display of the user interface screen with asecond user interface screen, wherein the substitution comprisesretaining one of the one or more of the indication of time and theoutline, wherein the retained indication of time or outline is displayedon the second user interface screen at a size larger than on the firstuser interface screen.

In some embodiments, a method comprises: receiving data relating to afirst subject matter; displaying first information relating to a firstportion of the received data; detecting a first rotation of a rotatableinput mechanism; and in response to detecting the first rotation of therotatable input mechanism, supplementing the first information withsecond information relating to a second portion of the received data.

In some embodiments, a non-transitory computer-readable storage mediumcomprises instructions for: receiving data relating to a first subjectmatter; displaying first information relating to a first portion of thereceived data; detecting a first rotation of a rotatable inputmechanism; and in response to detecting the first rotation of therotatable input mechanism, supplementing the first information withsecond information relating to a second portion of the received data.

In some embodiments, a transitory computer-readable storage mediumcomprises instructions for: receiving data relating to a first subjectmatter; displaying first information relating to a first portion of thereceived data; detecting a first rotation of a rotatable inputmechanism; and in response to detecting the first rotation of therotatable input mechanism, supplementing the first information withsecond information relating to a second portion of the received data.

In some embodiments, a device comprises: a display; a rotatable inputmechanism; one or more processors; and memory. In some embodiments, thememory stores instructions that, when executed by the one or moreprocessors, cause the one or more processors to: receive data relatingto a first subject matter; display first information relating to a firstportion of the received data; detect a first rotation of the rotatableinput mechanism; and, in response to detecting the first rotation of therotatable input mechanism, supplementing the first information withsecond information relating to a second portion of the received data.

In some embodiments, a device comprises: means for receiving datarelating to a first subject matter; means for displaying firstinformation relating to a first portion of the received data; means fordetecting a first rotation of the rotatable input mechanism; and meansfor, in response to detecting the first rotation of the rotatable inputmechanism, supplementing the first information with second informationrelating to a second portion of the received data.

In some embodiments, an electronic device comprises: a display unit; arotatable input mechanism unit; and a processing unit coupled to thedisplay unit and the rotatable input mechanism unit. In someembodiments, the processing unit is configured to: receive data relatingto a first subject matter; enable display on the display unit of firstinformation relating to a first portion of the received data; detect afirst rotation of the rotatable input mechanism unit; and, in responseto detecting the first rotation of the rotatable input mechanism unit,supplement the first information with second information relating to asecond portion of the received data.

In some embodiments, a method at an electronic device with a displaycomprises: obtaining first event data from a first application;obtaining second event data from a second application distinct from thefirst application; determining a first time value associated with thefirst event data and a second time value associated with the secondevent data and a relative order of the first time value and the secondtime value; and displaying, on the display, a user interface including:a representation of the first event data with a representation of thefirst time value; and a representation of the second event data with arepresentation of the second time value, wherein the representation ofthe first event data and the representation of the second event data aredisplayed with respect to each other in accordance with the relativeorder of the first time value and the second time value and therespective values of the first time value and the second time value.

In some embodiments, a non-transitory computer readable storage mediumstoring one or more programs, the one or more programs comprisinginstructions, which when executed by an electronic device with atouch-sensitive display cause the device to: obtain first event datafrom a first application; obtain second event data from a secondapplication distinct from the first application; determine a first timevalue associated with the first event data and a second time valueassociated with the second event data and a relative order of the firsttime value and the second time value; and display, on the display, auser interface including: a representation of the first event data witha representation of the first time value; and a representation of thesecond event data with a representation of the second time value,wherein the representation of the first event data and therepresentation of the second event data are displayed with respect toeach other in accordance with the relative order of the first time valueand the second time value and the respective values of the first timevalue and the second time value.

In some embodiments, a transitory computer readable storage mediumstoring one or more programs, the one or more programs comprisinginstructions, which when executed by an electronic device with atouch-sensitive display cause the device to: obtain first event datafrom a first application; obtain second event data from a secondapplication distinct from the first application; determine a first timevalue associated with the first event data and a second time valueassociated with the second event data and a relative order of the firsttime value and the second time value; and display, on the display, auser interface including: a representation of the first event data witha representation of the first time value; and a representation of thesecond event data with a representation of the second time value,wherein the representation of the first event data and therepresentation of the second event data are displayed with respect toeach other in accordance with the relative order of the first time valueand the second time value and the respective values of the first timevalue and the second time value.

In some embodiments, an electronic device, comprises: a touch-sensitivedisplay; one or more processors; memory; and one or more programs,wherein the one or more programs are stored in the memory and configuredto be executed by the one or more processors, the one or more programsincluding instructions, which when executed by the one or moreprocessors, cause the device to: obtain first event data from a firstapplication; obtain second event data from a second application distinctfrom the first application; determine a first time value associated withthe first event data and a second time value associated with the secondevent data and a relative order of the first time value and the secondtime value; and display, on the display, a user interface including: arepresentation of the first event data with a representation of thefirst time value; and a representation of the second event data with arepresentation of the second time value, wherein the representation ofthe first event data and the representation of the second event data aredisplayed with respect to each other in accordance with the relativeorder of the first time value and the second time value and therespective values of the first time value and the second time value.

In some embodiments, an electronic device, comprises: means forobtaining first event data from a first application; means for obtainingsecond event data from a second application distinct from the firstapplication; means for determining a first time value associated withthe first event data and a second time value associated with the secondevent data and a relative order of the first time value and the secondtime value; and means for displaying, on a touch sensitive display ofthe device, a user interface including: a representation of the firstevent data with a representation of the first time value; and arepresentation of the second event data with a representation of thesecond time value, wherein the representation of the first event dataand the representation of the second event data are displayed withrespect to each other in accordance with the relative order of the firsttime value and the second time value and the respective values of thefirst time value and the second time value.

In some embodiments, an electronic device, comprises: a display unitconfigured to display a graphic user interface; a touch-sensitivesurface unit configured to receive contacts; and a processing unitcoupled to the display unit, the touch-sensitive surface unit, therotatable and depressible input mechanism unit, and the button unit, theprocessing unit configured to: obtain first event data from a firstapplication; obtain second event data from a second application distinctfrom the first application; determine a first time value associated withthe first event data and a second time value associated with the secondevent data and a relative order of the first time value and the secondtime value; and display, on the display, a user interface including: arepresentation of the first event data with a representation of thefirst time value; and a representation of the second event data with arepresentation of the second time value, wherein the representation ofthe first event data and the representation of the second event data aredisplayed with respect to each other in accordance with the relativeorder of the first time value and the second time value and therespective values of the first time value and the second time value.

Thus, devices are provided with faster, more efficient methods andinterfaces for managing (e.g., editing) context-specific userinterfaces, thereby increasing the effectiveness, efficiency, and usersatisfaction with such devices. Such methods and interfaces maycomplement or replace other methods for managing context-specific userinterfaces.

DESCRIPTION OF THE FIGURES

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having atouch-sensitive display in accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIGS. 4A and 4B illustrate an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 5A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display and a rotatable and depressible inputmechanism in accordance with some embodiments.

FIG. 5B illustrates a portable multifunction device having atouch-sensitive display and a rotatable and depressible input mechanismin accordance with some embodiments.

FIGS. 6A and 6B illustrate exemplary context-specific user interfaces.

FIGS. 7A and 7B illustrate exemplary context-specific user interfaces.

FIG. 8 illustrates exemplary context-specific user interfaces.

FIG. 9 illustrates exemplary context-specific user interfaces.

FIG. 10 illustrates exemplary context-specific user interfaces.

FIGS. 11A-11C illustrate exemplary context-specific user interfaces.

FIG. 12 illustrates exemplary context-specific user interfaces.

FIGS. 13A and 13B illustrate exemplary context-specific user interfaces.

FIG. 14A illustrates exemplary context-specific user interfaces.

FIGS. 14B-14U illustrate exemplary context-specific user interfaces.

FIG. 15 illustrates exemplary context-specific user interfaces.

FIGS. 16A-16G illustrate exemplary context-specific user interfaces.

FIGS. 17A and 17B illustrate exemplary context-specific user interfaces.

FIGS. 18A-18C illustrate exemplary context-specific user interfaces.

FIG. 19 illustrates exemplary context-specific user interfaces.

FIG. 20 is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 21 is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 22 is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 23 is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 24 is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 25 is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 26 is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 27A is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 27B is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 27C is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 27D is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 27E is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 27F is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 28 is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 29 is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 30 is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 31 is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 32 is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 33 is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 34 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 35 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 36 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 37 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 38 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 39 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 40 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 41 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 42 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 43 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 44 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 45 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 46 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 47 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 48 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 49 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 50 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 51 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIG. 52 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIGS. 53A-53F illustrate exemplary user interfaces in accordance withsome embodiments.

FIGS. 54A-54E are flow diagrams illustrating methods of activating amode of operation in accordance with some embodiments.

FIG. 55 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIGS. 56A-56I illustrate exemplary context-specific user interfaces.

FIG. 57A is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 57B is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 57C is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 57D is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 57E is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 57F is a flow diagram illustrating a process for context-specificuser interfaces.

FIG. 58 is a functional block diagram of an electronic device inaccordance with some embodiments.

FIGS. 59A-59F illustrate exemplary user interfaces in accordance withsome embodiments.

FIGS. 60A-60F are flow diagrams illustrating a process for supplementingdisplayed information in accordance with some embodiments.

FIG. 61 is a functional block diagram of an electronic device inaccordance with some embodiments.

DETAILED DESCRIPTION

The following description sets forth exemplary methods, parameters andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

As discussed above, a user may customize context-specific userinterfaces for keeping time and receiving certain types of information.It is challenging to provide the user a multitude of options forcustomizing such interfaces while providing highly usable interfaces.Moreover, it is also challenging to present options for customizingnumerous variables such as color, display density, complications, and soforth in a way that is readily comprehensible and intuitive to the user.Context-specific user interfaces, and cohesive methods for allowing usercustomization of such interfaces, are highly desirable for portablemultifunction devices.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5B provide a description ofexemplary devices for performing the techniques for providingcontext-specific user interfaces. FIGS. 6-19 illustrate exemplarycontext-specific user interfaces. The user interfaces in the figures arealso used to illustrate the processes described below, including theprocesses in FIGS. 20-33.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a”, “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” may be construed to mean “when” or “upon” or “in responseto determining” or “in response to detecting,” depending on the context.Similarly, the phrase “if it is determined” or “if [a stated conditionor event] is detected” may be construed to mean “upon determining” or“in response to determining” or “upon detecting [the stated condition orevent]” or “in response to detecting [the stated condition or event],”depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device may support a variety of applications, such as one or more ofthe following: a drawing application, a presentation application, a wordprocessing application, a website creation application, a disk authoringapplication, a spreadsheet application, a gaming application, atelephone application, a video conferencing application, an e-mailapplication, an instant messaging application, a workout supportapplication, a photo management application, a digital cameraapplication, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 may include one or more computer-readable storage mediums.The computer-readable storage mediums may be tangible andnon-transitory. Memory 102 may include high-speed random access memoryand may also include non-volatile memory, such as one or more magneticdisk storage devices, flash memory devices, or other non-volatilesolid-state memory devices. Memory controller 122 may control access tomemory 102 by other components of device 100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 may be implemented ona single chip, such as chip 104. In some other embodiments, they may beimplemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data may be retrievedfrom and/or transmitted to memory 102 and/or RF circuitry 108 byperipherals interface 118. In some embodiments, audio circuitry 110 alsoincludes a headset jack (e.g., 212, FIG. 2). The headset jack providesan interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161, and one or more input controllers 160for other input or control devices. The one or more input controllers160 receive/send electrical signals from/to other input control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 160 are, optionally, coupled to any (ornone) of the following: a keyboard, an infrared port, a USB port, and apointer device such as a mouse. The one or more buttons (e.g., 208, FIG.2) optionally include an up/down button for volume control of speaker111 and/or microphone 113. The one or more buttons optionally include apush button (e.g., 206, FIG. 2).

A quick press of the push button may disengage a lock of touch screen112 or begin a process that uses gestures on the touch screen to unlockthe device, as described in U.S. patent application Ser. No. 11/322,549,“Unlocking a Device by Performing Gestures on an Unlock Image,” filedDec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated byreference in its entirety. A longer press of the push button (e.g., 206)may turn power to device 100 on or off. The user may be able tocustomize a functionality of one or more of the buttons. Touch screen112 is used to implement virtual or soft buttons and one or more softkeyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output may includegraphics, text, icons, video, and any combination thereof (collectivelytermed “graphics”). In some embodiments, some or all of the visualoutput may correspond to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 may use LCD (liquid crystal display) technology, LPD(light emitting polymer display) technology, or LED (light emittingdiode) technology, although other display technologies may be used inother embodiments. Touch screen 112 and display controller 156 maydetect contact and any movement or breaking thereof using any of aplurality of touch sensing technologies now known or later developed,including but not limited to capacitive, resistive, infrared, andsurface acoustic wave technologies, as well as other proximity sensorarrays or other elements for determining one or more points of contactwith touch screen 112. In an exemplary embodiment, projected mutualcapacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 may beanalogous to the multi-touch sensitive touchpads described in thefollowing U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No.6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 may beas described in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 may have a video resolution in excess of 100 dpi. Insome embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user may make contact with touch screen 112using any suitable object or appendage, such as a stylus, a finger, andso forth. In some embodiments, the user interface is designed to workprimarily with finger-based contacts and gestures, which can be lessprecise than stylus-based input due to the larger area of contact of afinger on the touch screen. In some embodiments, the device translatesthe rough finger-based input into a precise pointer/cursor position orcommand for performing the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100 mayinclude a touchpad (not shown) for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad may be a touch-sensitive surface that is separatefrom touch screen 112 or an extension of the touch-sensitive surfaceformed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 may include a power management system, oneor more power sources (e.g., battery, alternating current (AC)), arecharging system, a power failure detection circuit, a power converteror inverter, a power status indicator (e.g., a light-emitting diode(LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 may also include one or more optical sensors 164. FIG. 1Ashows an optical sensor coupled to optical sensor controller 158 in I/Osubsystem 106. Optical sensor 164 may include charge-coupled device(CCD) or complementary metal-oxide semiconductor (CMOS)phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 may capture stillimages or video. In some embodiments, an optical sensor is located onthe back of device 100, opposite touch screen display 112 on the frontof the device so that the touch screen display may be used as aviewfinder for still and/or video image acquisition. In someembodiments, an optical sensor is located on the front of the device sothat the user's image may be obtained for video conferencing while theuser views the other video conference participants on the touch screendisplay. In some embodiments, the position of optical sensor 164 can bechanged by the user (e.g., by rotating the lens and the sensor in thedevice housing) so that a single optical sensor 164 may be used alongwith the touch screen display for both video conferencing and stilland/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 may also include one or more proximity sensors 166. FIG. 1Ashows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 may be coupled to input controller 160in I/O subsystem 106. Proximity sensor 166 may perform as described inU.S. patent application Ser. No. 11/241,839, “Proximity Detector InHandheld Device”; Ser. No. 11/240,788, “Proximity Detector In HandheldDevice”; Ser. No. 11/620,702, “Using Ambient Light Sensor To AugmentProximity Sensor Output”; Ser. No. 11/586,862, “Automated Response ToAnd Sensing Of User Activity In Portable Devices”; and Ser. No.11/638,251, “Methods And Systems For Automatic Configuration OfPeripherals,” which are hereby incorporated by reference in theirentirety. In some embodiments, the proximity sensor turns off anddisables touch screen 112 when the multifunction device is placed nearthe user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 may also include one or more accelerometers 168. FIG. 1Ashows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 may be coupled to an input controller 160in I/O subsystem 106. Accelerometer 168 may perform as described in U.S.Patent Publication No. 20050190059, “Acceleration-based Theft DetectionSystem for Portable Electronic Devices,” and U.S. Patent Publication No.20060017692, “Methods And Apparatuses For Operating A Portable DeviceBased On An Accelerometer,” both of which are incorporated by referenceherein in their entirety. In some embodiments, information is displayedon the touch screen display in a portrait view or a landscape view basedon an analysis of data received from the one or more accelerometers.Device 100 optionally includes, in addition to accelerometer(s) 168, amagnetometer (not shown) and a GPS (or GLONASS or other globalnavigation system) receiver (not shown) for obtaining informationconcerning the location and orientation (e.g., portrait or landscape) ofdevice 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3)stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which may be a component of graphics module 132,provides soft keyboards for entering text in various applications (e.g.,contacts 137, e-mail 140, IM 141, browser 147, and any other applicationthat needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 may include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which may include one or more of: weather        widget 149-1, stocks widget 149-2, calculator widget 149-3,        alarm clock widget 149-4, dictionary widget 149-5, and other        widgets obtained by the user, as well as user-created widgets        149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that may be stored in memory 102include other word processing applications, other image editingapplications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 may be used to manage an address book orcontact list (e.g., stored in application internal state 192 of contactsmodule 137 in memory 102 or memory 370), including: adding name(s) tothe address book; deleting name(s) from the address book; associatingtelephone number(s), e-mail address(es), physical address(es) or otherinformation with a name; associating an image with a name; categorizingand sorting names; providing telephone numbers or e-mail addresses toinitiate and/or facilitate communications by telephone 138, videoconference module 139, e-mail 140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 may be used to enter a sequence of characters correspondingto a telephone number, access one or more telephone numbers in contactsmodule 137, modify a telephone number that has been entered, dial arespective telephone number, conduct a conversation, and disconnect orhang up when the conversation is completed. As noted above, the wirelesscommunication may use any of a plurality of communications standards,protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages may include graphics, photos, audio files, video filesand/or other attachments as are supported in an MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, orIMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that may be downloaded and used by a user (e.g.,weather widget 149-1, stocks widget 149-2, calculator widget 149-3,alarm clock widget 149-4, and dictionary widget 149-5) or created by theuser (e.g., user-created widget 149-6). In some embodiments, a widgetincludes an HTML (Hypertext Markup Language) file, a CSS (CascadingStyle Sheets) file, and a JavaScript file. In some embodiments, a widgetincludes an XML (Extensible Markup Language) file and a JavaScript file(e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150may be used by a user to create widgets (e.g., turning a user-specifiedportion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154may be used to receive, display, modify, and store maps and dataassociated with maps (e.g., driving directions, data on stores and otherpoints of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules may be combined or otherwiserearranged in various embodiments. For example, video player module maybe combined with music player module into a single module (e.g., videoand music player module 152, FIG. 1A). In some embodiments, memory 102may store a subset of the modules and data structures identified above.Furthermore, memory 102 may store additional modules and data structuresnot described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 may be reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., inoperating system 126) and a respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected may correspond to programmatic levels within aprogrammatic or view hierarchy of the application. For example, thelowest level view in which a touch is detected may be called the hitview, and the set of events that are recognized as proper inputs may bedetermined based, at least in part, on the hit view of the initial touchthat begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 may utilize or call data updater 176,object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which may include sub-event delivery instructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation may also include speed and direction of the sub-event. Insome embodiments, events include rotation of the device from oneorientation to another (e.g., from a portrait orientation to a landscapeorientation, or vice versa), and the event information includescorresponding information about the current orientation (also calleddevice attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers may interact, or are enabled to interact, with one another.In some embodiments, metadata 183 includes configurable properties,flags, and/or lists that indicate whether sub-events are delivered tovarying levels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 may also include one or more physical buttons, such as “home”or menu button 204. As described previously, menu button 204 may be usedto navigate to any application 136 in a set of applications that may beexecuted on device 100. Alternatively, in some embodiments, the menubutton is implemented as a soft key in a GUI displayed on touch screen112.

In one embodiment, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 may be stored in one ormore of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules may be combined or otherwise rearranged invarious embodiments. In some embodiments, memory 370 may store a subsetof the modules and data structures identified above. Furthermore, memory370 may store additional modules and data structures not describedabove.

Attention is now directed towards embodiments of user interfaces thatmay be implemented on, for example, portable multifunction device 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces may be implemented on device300. In some embodiments, user interface 400 includes the followingelements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 may optionally be labeled “Music” or “Music Player.” Otherlabels are, optionally, used for various application icons. In someembodiments, a label for a respective application icon includes a nameof an application corresponding to the respective application icon. Insome embodiments, a label for a particular application icon is distinctfrom a name of an application corresponding to the particularapplication icon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 357) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 359 for generating tactile outputsfor a user of device 300.

Although some of the examples which follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface) may haveone or more intensity sensors for detecting intensity of contacts (e.g.,touches) being applied. The one or more intensity sensors of touchscreen 504 (or the touch-sensitive surface) can provide output data thatrepresents the intensity of touches. The user interface of device 500can respond to touches based on their intensity, meaning that touches ofdifferent intensities can invoke different user interface operations ondevice 500.

Techniques for detecting and processing touch intensity may be found,for example, in related applications: International Patent ApplicationSerial No. PCT/US2013/040061, titled “Device, Method, and Graphical UserInterface for Displaying User Interface Objects Corresponding to anApplication,” filed May 8, 2013, published as WIPO Publication No.WO/2013/169849, and International Patent Application Serial No.PCT/US2013/069483, titled “Device, Method, and Graphical User Interfacefor Transitioning Between Touch Input to Display Output Relationships,”filed Nov. 11, 2013, published as WIPO Publication No. WO/2014/105276,each of which is hereby incorporated by reference in their entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms may permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, touch-intensity sensitive component 524. In addition, I/Osection 514 can be connected with communication unit 530 for receivingapplication and operating system data, using Wi-Fi, Bluetooth, nearfield communication (NFC), cellular, and/or other wireless communicationtechniques. Device 500 can include input mechanisms 506 and/or 508.Input mechanism 506 may be a rotatable input device or a depressible androtatable input device, for example. Input mechanism 508 may be abutton, in some examples.

Input mechanism 508 may be a microphone, in some examples. Personalelectronic device 500 can include various sensors, such as GPS sensor532, accelerometer 534, directional sensor 540 (e.g., compass),gyroscope 536, motion sensor 538, and/or a combination thereof, all ofwhich can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can be a non-transitorycomputer-readable storage medium, for storing computer-executableinstructions, which, when executed by one or more computer processors516, for example, can cause the computer processors to perform thetechniques described above, including processes 2000-3300 (FIGS. 20-33).The computer-executable instructions can also be stored and/ortransported within any non-transitory computer-readable storage mediumfor use by or in connection with an instruction execution system,apparatus, or device, such as a computer-based system,processor-containing system, or other system that can fetch theinstructions from the instruction execution system, apparatus, or deviceand execute the instructions. For purposes of this document, a“non-transitory computer-readable storage medium” can be any medium thatcan tangibly contain or store computer-executable instructions for useby or in connection with the instruction execution system, apparatus, ordevice. The non-transitory computer-readable storage medium can include,but is not limited to, magnetic, optical, and/or semiconductor storages.Examples of such storage include magnetic disks, optical discs based onCD, DVD, or Blu-ray technologies, as well as persistent solid-statememory such as flash, solid-state drives, and the like. Personalelectronic device 500 is not limited to the components and configurationof FIG. 5B, but can include other or additional components in multipleconfigurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that may be displayed on the displayscreen of devices 100, 300, and/or 500 (FIGS. 1, 3, and 5). For example,an image (e.g., icon), a button, and text (e.g., hyperlink) may eachconstitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionallybased on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholds mayinclude a first intensity threshold and a second intensity threshold. Inthis example, a contact with a characteristic intensity that does notexceed the first threshold results in a first operation, a contact witha characteristic intensity that exceeds the first intensity thresholdand does not exceed the second intensity threshold results in a secondoperation, and a contact with a characteristic intensity that exceedsthe second threshold results in a third operation. In some embodiments,a comparison between the characteristic intensity and one or morethresholds is used to determine whether or not to perform one or moreoperations (e.g., whether to perform a respective operation or forgoperforming the respective operation) rather than being used to determinewhether to perform a first operation or a second operation.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface may receive a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location may be basedon only a portion of the continuous swipe contact, and not the entireswipe contact (e.g., only the portion of the swipe contact at the endlocation). In some embodiments, a smoothing algorithm may be applied tothe intensities of the swipe contact prior to determining thecharacteristic intensity of the contact. For example, the smoothingalgorithm optionally includes one or more of: an unweightedsliding-average smoothing algorithm, a triangular smoothing algorithm, amedian filter smoothing algorithm, and/or an exponential smoothingalgorithm. In some circumstances, these smoothing algorithms eliminatenarrow spikes or dips in the intensities of the swipe contact forpurposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface may becharacterized relative to one or more intensity thresholds, such as acontact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

As used herein, an “installed application” refers to a softwareapplication that has been downloaded onto an electronic device (e.g.,devices 100, 300, and/or 500) and is ready to be launched (e.g., becomeopened) on the device. In some embodiments, a downloaded applicationbecomes an installed application by way of an installation program thatextracts program portions from a downloaded package and integrates theextracted portions with the operating system of the computer system.

As used herein, the term “open application” or “executing application”refers to a software application with retained state information (e.g.,as part of device/global internal state 157 and/or application internalstate 192). An open or executing application may be any one of thefollowing types of applications:

-   -   an active application, which is currently displayed on a display        screen of the device that the application is being used on;    -   a background application (or background processes), which is not        currently displayed, but one or more processes for the        application are being processed by one or more processors; and    -   a suspended or hibernated application, which is not running, but        has state information that is stored in memory (volatile and        non-volatile, respectively) and that can be used to resume        execution of the application.

As used herein, the term “closed application” refers to softwareapplications without retained state information (e.g., state informationfor closed applications is not stored in a memory of the device).Accordingly, closing an application includes stopping and/or removingapplication processes for the application and removing state informationfor the application from the memory of the device. Generally, opening asecond application while in a first application does not close the firstapplication. When the second application is displayed and the firstapplication ceases to be displayed, the first application becomes abackground application.

1. Context-Specific User Interfaces

Attention is now directed towards embodiments of context-specific userinterfaces (“UI”) and associated processes that may be implemented on amultifunction device with a display and a touch-sensitive surface, suchas devices 100, 300, and/or 500 (FIGS. 1A, 3A, and/or 5A).

The following examples illustrate exemplary embodiments ofcontext-specific user interfaces. Described herein are overall conceptsrelated to customizable context-specific user interfaces. It is notedthat the context-specific user interfaces described herein are editablein a number of ways. A user interface may display or otherwise indicatevarious types of information related to time, and the type(s) ofinformation may be customizable by the user. A user interface mayinclude aspects such as colors, density of display, and complications(or lack of complications) that are also customizable. As used here,consistent with its accepted meaning in art, a complication refers toany clock face feature other than those used to indicate the hours andminutes of a time (e.g., clock hands or hour/minute indications).Complications may provide different types of information to a user, suchas data obtained from an application, and the information conveyed to auser by a complication is also customizable, as described below.

These combinatorial features result in many thousands, if not more, ofavailable context-specific user interfaces. Since describing each ofthese permutations is not practical, particular aspects are highlightedwith particular context-specific user interfaces, but these exemplarydescriptions are in no way intended to limit such aspects to suchcontext-specific user interfaces, as specific aspects may be used inother context-specific user interfaces, and specific context-specificuser interfaces may have other aspects. These embodiments are meant toillustrate the overall concepts presented, but a skilled artisan willrecognize that numerous other embodiments are possible within the scopeof the techniques described herein.

FIG. 6A shows an exemplary context-specific user interface that may beoperated on device 600. Device 600 may be device 100, 300, or 500 insome embodiments. The electronic device has a display (e.g., 504).

A user keeping track of the time of day may wish to gain some sense ofhow much time has elapsed since a particular event. For example, a usermay wish to know how much time has elapsed since the last time the userviewed the time, or how much time has elapsed since a particular time ofday, like morning. In addition to viewing a clock face, the user maywish to receive additional visual cues that reinforce the perception ofelapsed time.

As shown in FIG. 6A, the device receives data representing user input602. In response to receiving the data, the device displays userinterface screen 604 on the display. Screen 604 includes clock face 606.In the example illustrated in FIG. 6A, the time is currently 7:00. Clockface 606 initially indicates a first time (10:05 as shown in FIG. 6A)that precedes the current time. Device 600 updates screen 604 byanimating the clock face to transition from indicating the first time toindicating the current time. Updated screen 604 is depicted as screen610, which displays clock face 612. Clock face 612 has been updated toindicate the current time. The animation from screens 604 to 610represents the passage of time from the first time to the current time.In some embodiments, screen 604 and/or 610 may also include anindication of the date.

As described above, the context-specific user interface exemplified inFIG. 6A first displays the clock face indicating a first time. The firsttime may be determined based on different criteria. In some embodiments,the device receives second data representing a time of a previous usermovement of the electronic device (e.g., a movement of the device suchas a lowering of the user's wrist, if the device is wearable, or othermovement indicative that the user is no longer actively viewing thedisplay). The time of the previous user movement of the device may bethe last time the user looked at the device, or the last time thedisplay of the device was turned off, prior to receiving the datarepresenting user input 602. The time of the previous user movement ofthe electronic device is then shown as the first time indicated by theclock face. For example, in FIG. 6A, 10:05 depicted by clock face 606may be the time of a previous user movement of the device, indicatingthe time of a previous user interaction. In these examples, when theuser interface screen updates, it provides the user an indication of howmuch time has elapsed since the previous user interaction (e.g., thelast time the user looked at device 600).

In other embodiments, the first time may be based on a predeterminedinterval of time. For example, the first time may precede the currenttime by a first duration, and the first duration may be a predeterminedduration before the current time. That is to say, rather than beingbased on a user interaction, the first time indicated by the clock facemay be based on a predetermined or fixed duration before the currenttime.

In some embodiments, the predetermined duration is 5 hours. In responseto user input, the clock face may depict a time 5 hours before thecurrent time, then animate the clock face to transition from indicatingthe first time to indicating the current time. For example, if thecurrent time is 6:00, the device may, in response to user input, displaya clock face showing 1:00 that is animated to transition from 1:00 to6:00.

In other embodiments, the first time may be based on a predeterminedtime of day. In this case, the device may begin the animation byindicating the same time of day (i.e., the first time) no matter thecurrent time, and then animate the clock face until it reaches thecurrent time. For example, the first time may be morning (e.g., 8:00am). In this example, if the current time is 6:00, the device may, inresponse to user input, display a clock face showing 8:00 that isanimated to transition from 8:00 to 6:00.

Regardless of how the first time is determined, in some embodiments, theclock face may be animated for a period of time indicative of theduration between the first time and the current time. That is to say,the length of the animation may be roughly proportional to the length ofthis duration. The length of animation may not be precisely proportionalto the first duration, but rather it may convey to the user a generalindication of an approximate length of the time. To illustrate using theexamples described above, the clock face may be animated for a longerperiod of time if transitioning from 8:00 to 6:00 than it is iftransitioning from 3:00 to 6:00. This may be particularly useful if theduration is variable, such as if the duration is based on the timebetween user interactions. In this case, a user will immediatelycomprehend that the time elapsed between interactions is longer if theanimation of the clock face is longer, or that the time betweeninteractions is shorter if the animation of the clock face is shorter.

In other embodiments, the clock face is animated for a period of timeindependent of the first duration. That is to say, the length of theanimation is not proportional to the duration between the first time andthe current time. In some embodiments, the length of animation may bethe same for each animation. To illustrate using the examples describedabove, the clock face may be animated for the same period of timeregardless if transitioning from 8:00 to 6:00 or from 3:00 to 6:00. Thismay be helpful to reduce the time a user is viewing the transition.Alternatively, the clock face is animated for a different period of timeif transitioning from 8:00 to 6:00 compared to transitioning from 3:00to 6:00, but the periods of time may not related to the first duration.

FIG. 6B illustrates optional features of this context-specific userinterface. In response to data representing user input 620, device 600displays user interface screen 622, which includes clock face 624. Inthis example, the current time is 10:25. Clock face 624 indicates afirst time (in this example, 10:05). As a background, clock face 624also displays an image of a mountain scene that is representative of thefirst time. For example, as shown in FIG. 6B, clock face 624 shows amorning view of the mountain scene (see, e.g., the position of sun 626in the sky). Therefore, a user viewing clock face 624 understands thetime based on the clock face itself and the background, which alsorepresents the time indicated by the clock face. Note that this providesadditional information to the user because the user understands that theindicated time is 10:05 am, not 10:05 pm, by the display of the scene.

In some embodiments, the device accesses an image of a scene that isrepresentative of the time indicated by the clock face. An image of ascene that is representative of a time may connote to the user a similartime of day, in conjunction with the time indicated by the clock face.The image of the scene need not connote the precise time indicated bythe clock face, nor does it need to be strictly linked to the time ofday at the location of the scene (this will be discussed in greaterdetail below). In some embodiments, the image of the scene is an imagecaptured at substantially the same time of day as the current time(i.e., the time of day when the image was taken at the scene). In otherembodiments, the image of the scene is an image captured at a differenttime of day, as compared to the current time.

In some embodiments, the image of the scene may depict, for example, acity, beach, desert, park, lake, mountain, or valley. In someembodiments, the scene may be recognizable to the user, such as a sceneof Yosemite Valley or Big Ben.

Device 600 then displays screens 630 and 640. Screen 630 is optional, asdescribed below, and includes clock face 632, which is indicating a timebetween the first time and the current time. This intermediate time isfurther represented on clock face 632 by the background (see, e.g.,setting sun 634). Screen 640 includes clock face 642, which depicts thecurrent time. Clock face 642 also displays a background that representsthe current time (see, e.g., moon 644).

Therefore, in some embodiments, and in response to receiving datarepresenting user input 620, the device accesses a first image of ascene representative of the first time (e.g., the background of clockface 624), accesses a second image of the scene representative of thecurrent time (e.g., the background of clock face 642), and in responseto receiving the data representing the user input, successively displaysthe first image of the scene and the second image of the scene.

The successive display indicates the passage of time from the first timeto the current time. The device may include a series of images for aparticular scene (e.g., time lapse images), each depicting a differenttime of day, such that any first time or current time depicted by theclock face has a corresponding image of the scene that is representativeof the depicted time. In some embodiments, the first image of the sceneand the second image of the scene are displayed as backgrounds on theuser interface screen.

In some embodiments, the device accesses a sequence of images of a scenethat includes a first image of the scene representative of the firsttime (e.g., the background of clock face 624), one or more second imagesof the scene representative of one or more times between the first timeand the current time (e.g., the background of clock face 632), and athird image of the scene representative of the current time (e.g., thebackground of clock face 642). In response to receiving the datarepresenting user input 620, the device displays the sequence of imagesof the scene by animating the sequence of images to indicate the passageof time from the first time to the current time (e.g., like a flipbook).In some embodiments, the scene is user-designated (e.g., the device maystore a set of time lapse images for different scenes, and the user mayselect the scene to be displayed).

As shown in FIG. 6B, device 600 sequentially displays screens 622, 630,and 640 to animate the displayed, respective backgrounds, therebyanimating the image of the scene like a flipbook to indicate the passageof time. In some embodiments, the transition from screen 620 to 630 to640 may also be animated, e.g., by animating the hands of the clock faceto rotate in a clockwise manner, and/or by animating the display of theimages of the scene, as with a flipbook. If the clock face instead oradditionally depicts a representation of a digital clock, the numericalindications of the hour and the minute may be animated in some fashionto depict the passage of time. By displaying both the animated clockface and the animated image(s) of the scene, the device provides theuser a clearer and readily distinguishable indication of the timebetween the first time and the current time.

In some embodiments, device 600 has a location sensor (e.g., GPS sensor532 and/or GPS module 135), and the device obtains a current location ofthe device from the location sensor. The first image of the scenerepresents the first time at the current location, and the second imageor the third image of the scene (e.g., whichever is representative ofthe current time) represents the current time at the current location.That is to say, the indicated passage of time reflects day/night hoursat the current location. For example, if the user is at a location nearthe Arctic Circle, the current day may have daytime hours close to 24hours (e.g., midnight sun). In this example, the images indicating thefirst time and the current time may all be daytime images of the scene(e.g., Yosemite Valley), even if the first time and the current time areseparated by a long period of time. Therefore, the images of the scenemay be representative of the depicted time(s) at the current location,but they may not be representative of the depicted time(s) at thelocation of the scene. This concept allows the device to display acontext-specific user interface for depicting the passage of time at thecurrent location and enhances a user's interaction with the device,since the animation is grounded in the user's experience (e.g.,perception of time) at the current location.

In some embodiments, the device displays a user interface object on theuser interface screen at a first position based on the first time. Insome embodiments, the position may be based on a position along theclock face, like an hour indication (e.g., 6 o'clock position at thelower center of the display). In some embodiments, the position may bebased on a position across a horizon, such as a position of the Sun orthe Moon. For example, in FIG. 6B, the position of sun 626 indicates thefirst time because it represents the sun in the scene at a position inthe east just short of high noon.

In some embodiments, the device animates the user interface object bymoving the user interface object from the first position to a secondposition on the user interface screen, where the second position isbased on the current time. Moving the user interface object from thefirst position to a second position indicates the passage of time fromthe first time to the current time. As shown in FIG. 6B, sun 626 movesacross the sky in the sequence of images of the scene (cf. sun 626 andsun 634). The user interface object then depicts moon 644 at a positionin the night sky indicating the current time. In some embodiments, theuser interface object is a graphical representation of a sun (e.g., 626and 634). In some embodiments, the user interface object is a graphicalrepresentation of a moon (e.g., 644).

In any of the embodiments described above, the user input may include amovement of the device. For example, a movement of the device could beraising of the user's wrist (if the device is wearable), or othermovement indicative of the user raising the device to view the display.These movements could be detected, for example, by using anaccelerometer (e.g., 534), a gyroscope (e.g., 536), a motion sensor(e.g., 538), and/or a combination thereof. In any of thecontext-dependent faces described herein, a movement of the device maybe a user input that activates the display.

Further, in any of the context-dependent faces described herein, amovement of the device such as a lowering of the user's wrist (if thedevice is wearable) or other movement indicative that the user is nolonger actively viewing the display, or a lack of a movement of thedevice such as raising of the user's wrist (if the device is wearable)or other movement indicative of the user raising the device to view thedisplay, may be a user input that causes the device to turn off thedisplay.

In other embodiments, the device may have a touch-sensitive display ortouch-sensitive surface (e.g., touchpad 355 in FIG. 3, touch-sensitivesurface 451 in FIG. 4B, and/or touchscreen 504), and the user input maybe a contact on the touch-sensitive display.

Attention is now directed to the context-specific user interface shownin FIG. 7A. FIG. 7A shows exemplary context-specific user interfacesthat may be operated on device 700. Device 700 may be device 100, 300,or 500 in some embodiments. The electronic device has a touch-sensitivedisplay (e.g., touchscreen 504).

A user may wish to keep track of the time of day while also accessing astopwatch function. For example, in contexts such as running or cycling,a user may wish to operate a stopwatch, record laps, and still maintaina view of the time of day.

As shown in FIG. 7A, device 700 displays a clock face that indicatescurrent time, as depicted on user interface screen 702, on thetouch-sensitive display. The clock face includes hour hand and minutehand 704. The clock face also includes one or more indications of anhourly timescale (e.g., numbers 12, 1, 2, 3, and/or tick marks or othervisual indicators displayed at the corresponding positions on the clockface), such as 12 o'clock indicator 706. The clock face further includesstopwatch hand 708 (which, in some embodiments described below, alsoserves as a seconds hand. Note that, as used herein, the term secondshand refers to a hand on a clock face that indicates seconds, not asecond hand of two hands on a clock face).

As exemplified in FIG. 7A, device 700 receives user input, which in thiscase is touch 712 on start affordance 710. In response, the devicereplaces the 12 o'clock indicator 706 with stopwatch timescale indicator724, as shown on screen 720. Stopwatch indicator 724 shows that thestopwatch timescale is a 60 second timescale. A timescale for thestopwatch hand may refer to the amount of time needed for the stopwatchhand to complete one full revolution around the displayed clock face.Note that the clock face on screen 720 includes hour hand and minutehand 722 and stopwatch hand 726, which are the same as hour hand andminute hand 704 and stopwatch hand 708.

Further in response to touch 712, device 700 animates stopwatch hand 726to reflect passage of time, as shown by comparing screen 720 and 730. Asshown on screen 730, the stopwatch hand has moved to a second positionon the clock face (note the position of stopwatch hand 736), indicatingthe passage of time. Given that indicator 734 shows that the stopwatchtimescale is 60 seconds, the position of stopwatch hand 736 indicatesthat 25 seconds have passed. As shown in FIG. 7A, the user accesses thisinformation by touch 740 on lap affordance 738, which causes the displayof time 742, indicating the time elapsed since touch 712. Note that hourhand and minute hand 732 are the same as 722 and 704, and these twohands have not changed position in the last 25 seconds. In this example,the hour hand and minute hand are indicating the same time of day (e.g.,10:10) throughout screens 702, 720, and 730.

Stated another way, the device displays the time of day with the hourhand and the minute hand, and it additionally displays a stopwatch hand.In response to receiving data representing user input, the indication(s)of the hour are replaced with indication(s) of a first timescale of thestopwatch hand, but the hour hand and the minute hand continue toindicate the time of day, even though the hour indication(s) have beenreplaced. This allows the user to view a stopwatch and the time of daysimultaneously, while showing that the stopwatch has started andindicating the timescale for the stopwatch. Also in response toreceiving the data, the device animates the stopwatch hand to reflectpassage of time.

In some embodiments, while animating the stopwatch hand to reflect thepassage of time, the device receives second data representing a seconduser input, and in response to receiving the second data, the device maycease the animation of the stopwatch hand. For example, this mayfunction similar to a “stop” function for the stopwatch.

In some embodiments, the device may display on the touch-sensitivedisplay a first affordance representing a start/stop function (e.g.,affordance 710). The first data representing the first user input (e.g.,touch 712) and the second data representing the second user input bothrepresent contacts on the displayed first affordance. In otherembodiments, the device may display separate affordances for thestopwatch start and stopwatch stop functions.

In some embodiments, the device may display on the touch-sensitivedisplay a second affordance representing a lap function (e.g.,affordance 738). The devices receives third data representing a contacton the displayed second affordance after receiving the first data (e.g.,after invoking the start function) and before receiving the second data(e.g., before invoking the stop function). In response to receiving thethird data, the device displays a third numerical indication of elapsedtime between receiving the first data and receiving the third data. Forexample, this may function similar to a “lap” function for the stopwatchthat causes a display of the time elapsed since invoking the startfunction. As described above, this feature is illustrated on screen 730.

In some embodiments, the device may display on the touch-sensitivedisplay a third affordance representing a stopwatch application, whichis depicted as affordance 714 on screen 702. The device receives fourthdata representing a contact on the displayed third affordance, and inresponse to receiving the fourth data, the device launches the stopwatchapplication. This allows the user to access additional informationand/or functionality related to the stopwatch feature directly from thiscontext-specific user interface. In one embodiment, the stopwatchapplication is an application as described in related application: U.S.Provisional Patent Application Ser. No. 62/044,979, filed on Sep. 2,2014, entitled “Stopwatch and Timer User Interfaces.”

In some embodiments, the first timescale for the stopwatch hand may be60 seconds, 30 seconds, 6 seconds, or 3 seconds. In some embodiments,the movement of the stopwatch hand is animated at a rate based on thefirst timescale for the stopwatch hand. For example, the stopwatch handmay move faster if the timescale is 3 seconds than if the timescale is60 seconds. This allows the stopwatch hand to complete a full revolutionaround the clock face in the amount of time depicted by the firsttimescale.

In some embodiments, the device may substitute the one or moreindications of an hourly timescale with an indication of a firsttimescale for the stopwatch hand by removing the one or more indicationsof the hourly timescale, displaying the indication of the firsttimescale for the stopwatch hand, and translating the displayedindication of the first timescale for the stopwatch hand in a rotationalmotion in a clockwise direction. As an illustrative example, if thedisplay includes 12 numerical indications of hourly timescale, and thefirst timescale for the stopwatch hand is a 6 second timescale, thedevice may substitute the 12 numerals with a single 6 numeral. In someembodiments, this may be the same 6 numeral that was previously theindicator for the 6 o'clock hour, such that the substitute and displayare not perceptible to the user. The device may display the 6 numericalindicating the first timescale for the stopwatch hand at the 6 o'clockposition on the clock face, then translate the 6 in a clockwise motionaround the clock face until it arrives at the top of the clock face(formerly the 12 o'clock position), at which point the translationstops. This improves the context-specific interface by reinforcing tothe user that the clock face has transitioned from indicating hours andminutes to indicating the first timescale for the stopwatch hand.

As illustrated in FIG. 7B, in some embodiments, the device has arotatable input mechanism (e.g., 506), which may be used as an optionalinput to change the stopwatch timescale. FIG. 7B shows screen 750 withclock face 752, which includes hour hand and minute hand 754, andstopwatch timescale indicator 756 (showing a 60 second timescale). Inresponse to receiving fifth data representing movement of the rotatableinput mechanism (e.g., movement 758), the device 700 changes thestopwatch timescale to a second timescale, as shown by stopwatchtimescale indicator 776, part of clock face 772 on screen 770. Note thatscreen 770 continues to display hour hand and minute hand 774. Thesecond stopwatch timescale is different from the first stopwatchtimescale. This allows the user to customize the timescale for thestopwatch hand through rotating the rotatable input mechanism, allowingfor a context-specific user interface depending on the user's desiredstopwatch timescale.

In some embodiments, the device substitutes the indication of the firsttimescale for the stopwatch hand with the indication of the secondtimescale for the stopwatch hand by removing the indication of the firsttimescale for the stopwatch hand, displaying the indication of thesecond timescale for the stopwatch hand, and translating the displayedindication of the second timescale for the stopwatch hand in arotational motion in a clockwise direction.

As shown in FIG. 7B, indicator of the second timescale for the stopwatchhand 760 is displayed at a position on the clock face that indicates itsrelative position in the first timescale For example, indicator of a 30second timescale 760 is displayed on clock face 752 at a position basedon the sixty second timescale indicated by 756. In response to receivingdata representing movement 758, the device removes 756, displays 760,and translates 760 in a rotational motion in a clockwise direction untilit reaches the former position of the indicator of the first timescalefor the stopwatch hand (e.g., (e.g., the former position of 756, asdepicted by the position of 776 on clock face 772).

In some embodiments, after receiving the first data representing thefirst user input, the device animates the stopwatch hand to represent arotational motion about an origin and ceases the animation to displaythe stopwatch hand at a position at π/2 radians (e.g., the 12 o'clockposition) relative to the rotational motion about the origin. Forexample, the stopwatch hand may function as a seconds hand of the clockface before the first data is received. When the first data is received,the seconds hand may be animated to depict a rotation around the clockface (e.g., by rotating about the center point of the clock face) untilit resets at the 12 o'clock position. This signals to the user that theseconds hand has now become the stopwatch hand.

Attention is now directed to the context-specific user interface shownin FIG. 8. FIG. 8 shows exemplary context-specific user interfaces thatmay be operated on device 800. Device 800 may be device 100, 300, or 500in some embodiments. The electronic device has a touch-sensitive display(e.g., touchscreen 504).

FIGS. 8-10 provide context-specific user interfaces that allow the userto view the passage of time while accessing a rich array ofgeographical, lunar, and astronomical information. For example, a usermay have acquaintances all over the world and wish to know what parts ofthe world are in daytime or nighttime at a current time. A user may havean interest in the moon phase and wish to know what the Moon will looklike tomorrow, next week, or next month. A user may have an interest inastronomy and wish to know how the planets are aligned at a particulartime of interest, which could be the current day.

In FIG. 8, device 800 displays user interface screen 802 that includesfirst affordance 804. First affordance 804 represents a simulation of aregion of the Earth, as illuminated by the Sun at the current time. Forexample, first affordance 804 shows that North, Central, and SouthAmerica are currently in daytime, and part of the Pacific Ocean iscurrently in nighttime, thus simulating a region of the Earth asilluminated by the Sun at the current time.

Screen 802 also displays second affordance 806, which indicates thecurrent time. Second affordance 806 indicates the current time (10:09)and optionally includes an indication of the day of the week (Wednesday)and the day of the month (25^(th)). Screen 802 further displays moonaffordance 808 and solar system affordance 810, which are used to invokeadditional context-specific user interfaces accessible from this screenthat will be described in more detail below.

In some embodiments, the simulation of the first region of the Earth asilluminated by the Sun at the current time is a realistic rendering ofthe Earth at the current time. For example, the simulation of the Earthmay include specific geographic features. In some embodiments, thesimulation of the Earth is updated to reflect weather patterns at thecurrent time (e.g., by depicting cloud cover or other weather phenomenasuch as a tropical storm). The device may update the Earth to reflectglobal-scale by obtaining data from a weather service or externalserver, such as The Weather Channel, Accuweather, The National WeatherService, Yahoo! ™ Weather, Weather Underground, the United States NavalObservatory, or the National Oceanic and Atmospheric Administration. Insome embodiments, the simulation of the first region of the Earth asilluminated by the Sun at the current time may indicate other globalevents, such as the real-time position of the International SpaceStation, which may be obtained from a service or external server such asfrom NASA.

Device 800 receives a user input (in this example, swipe 812), and inresponse to receiving the user input, device 800 rotates the simulationof the Earth to display a second region of the Earth as illuminated bythe Sun at the current time. This is depicted on screen 820, whichdisplays first affordance 822 depicting a second region of the Earth asilluminated by the Sun at the current time, which is indicated by secondaffordance 824. This feature allows the user to access additionalinformation other than the current time from this context-specific userinterface. For example, a user is able to rotate the simulation of theEarth and display which regions are currently in daytime and whichregions are currently in nighttime. Tying this information to asimulation of the Earth allows the user to access complex geographicaland time-related data in a manner that is instantly intuitive andcomprehensible.

In some embodiments, the first affordance representing the simulation ofthe first region of the Earth as illuminated by the Sun at the currenttime includes a representation of a solar terminator (e.g., a day/nightline at the current time). As illustrated by affordances 804 and 822,the simulation of the Earth may include a depiction of a region of theEarth currently in daytime, a region of the Earth currently innighttime, and/or a solar terminator dividing the two regions.

In some embodiments, the user input includes a swipe on thetouch-sensitive display in a first swipe direction, as illustrated byswipe 812. This allows the user to swipe the display to rotate thesimulation of the Earth. In some embodiments, the direction of rotationof the Earth is the same as the swipe direction. In some embodiments,the direction of rotation of the Earth is the opposite as the swipedirection.

In some embodiments, the user may rotate the simulation of the Earth inmore than one direction using swipes in different directions. Forexample, a swipe in one direction may cause the representation of theEarth to rotate in one direction, and a swipe in an opposite orotherwise different direction may cause the representation of the Earthto rotate in an opposite direction. This allows the user to swipe indifferent directions to direct the rotation of the simulation of theEarth.

In some embodiments, as illustrated in FIG. 8, the device has arotatable input mechanism (e.g., 506). Device 800 receives user inputrepresenting a movement of the rotatable input mechanism (e.g., movement830), and in response, device 800 updates first affordance 822 torepresent a simulation of the first region of the Earth as illuminatedby the Sun at a non-current time. This is shown on screen 840 with firstaffordance 842 and second affordance 844. Comparing screens 820 and 840,the simulation of the Earth has been updated (cf. 822 and 842) fromindicating a region of the Earth at the current time (10:09, indicatedby 824) to indicating the same region of the Earth at a non-current time(12:09, indicated by 844). This feature provides the user access tofurther geographic and time-related information by allowing the user toview the Earth, as illuminated by the Sun, at various times throughoutthe day.

In some embodiments, the device has a location sensor (e.g., GPS sensor532 and/or GPS module 135), and before displaying the user interfacescreen, the device obtains a current location of the electronic devicefrom the location sensor and displays the first region of the Earthrepresented by the first affordance to indicate the current location ofthe electronic device. This allows the device to display the Earth insuch a way that the current location is part of the visible portion ofthe simulation of the Earth, for example as a default or user-selectablestate. In some embodiments, the first affordance includes a visualmarking of the current location on the representation of the Earth. Thisallows the user to easily identify the current location on thesimulation of the Earth.

In some embodiments, the device (e.g., device 800) visually marks thecurrent location of the device on the representation of the Earth (e.g.,by displaying a symbol at the appropriate location on the representationof the Earth and/or text indicating the current location). In someembodiments, this visual marking may be transitory, e.g., the visualmarking may be displayed briefly and then disappear or fade out. In someembodiments, while the user is at the current location, the device doesnot repeat the visual marking of the current location. However, if theuser changes locations, the first time the user looks at the displayafter changing location, the device will visually mark the new currentlocation on the representation of the Earth as set forth above. In someembodiments, the device detects a user movement of the device (e.g., amovement of the device such as raising of the user's wrist, if thedevice is wearable, or other movement indicative that the user isviewing the display) and in response obtains a current location of theelectronic device from the location sensor. The device may thendetermine whether the current location is the same as the location ofthe device at the last user movement of the device. In accordance with adetermination that the current location has changed since the last usermovement of the device, the device may visually mark the currentlocation on the representation of the Earth.

In some embodiments, the device visually marks a location (e.g., acurrent location) corresponding to the location of a contact (e.g., thelocation of the contact's electronic device) on the representation ofthe Earth (e.g., by displaying a symbol at the appropriate location onthe representation of the Earth and/or text indicating the contact'slocation). The contact may be stored, e.g., on the device or on anexternal device that is coupled to the device via wireless communication(e.g., Wi-Fi, Bluetooth™, near field communication (“NFC”), or any ofthe other cellular and/or other wireless communication techniquesdescribed herein). In some embodiments, the contact may be a contactassociated with a user that has agreed to provide their location data tothe user of device 800, such as through a Find My Friends application,and data indicating the location of the contact's electronic device maybe provided through a server, which may provide the location of thecontacts stored on device 800. This provides the user of device 800 aquick visual reference to alert them to the current location of acontact. In some embodiments, the user may further input the travelinformation for a contact (e.g., flight data for a contact traveling byair, train data, cruise or boat data, etc.). The device may obtain datarepresenting the current or predicted location of the contact (provided,e.g., by an airline's server in the example of flight data) and updatethe visual marking of the contact's location based on the obtained data.

In some embodiments, the device detects a user movement of the device(e.g., a movement of the device such as raising of the user's wrist, ifthe device is wearable, or other movement indicative that the user isviewing the display). In response to detecting the movement, the deviceanimates the first affordance representing the simulation of the Earthby translating the first affordance on-screen towards the center of thedisplayed user interface screen. For example, upon detecting a usermovement, the device animates the simulation of the Earth to rotate infrom a side or edge of the display to the center of the display.

In some embodiments, the device displays on the user interface screen athird affordance representing a moon (as depicted by affordances 808,826, and 846). In some embodiments, the third affordance may be agraphical or stylized representation of a moon such as an icon, symbol,or a text indicating a moon. In some embodiments, the third affordancemay be a realistic rendering of the Moon as seen from the Earth at thecurrent time with actual lunar features depicted.

The device detects a contact on the displayed third affordance, and inresponse to detecting the contact, the device updates the display of theuser interface screen by displaying a fourth affordance representing asimulation of the Moon as seen from the Earth at the current time and afifth affordance indicating the current time. In some embodiments,updating the display of the user interface screen includes animating thefirst affordance representing the simulation of the first region of theEarth as illuminated by the Sun by zooming out. This animation allowsthe user to recognize that the astronomical scale and/or perspective haschanged.

This transitions the user interface from providing information about thecurrent time within the current day using a simulation of the Earth toproviding information about the current time within the current monthusing a simulation of the Moon. Whereas the context-specific userinterface described in reference to FIG. 8 provides the user worldwide,customizable geographical information about day/night conditions, acontext-specific user interface that provides the user customizableinformation about moon phases and other lunar features is illustrated inFIG. 9.

FIG. 9 shows exemplary context-specific user interfaces that may beoperated on device 900. Device 900 may be device 100, 300, or 500 insome embodiments. The electronic device has a touch-sensitive display(e.g., touchscreen 504).

As described above, device 900 is device 800 with an updated display.Device 900 is displaying screen 902, which includes affordance 904.Affordance 904 represents a simulation of the Moon as seen from theEarth at the current time (e.g., the current moon phase). In someembodiments, fourth affordance 904 is a realistic rendering of the Moonas seen from the Earth at the current time with actual lunar featuresdepicted. As shown by fourth affordance 904, the current moon phase is awaning crescent moon. Although FIG. 9 shows a stylized crescent moon forthe representation of the Moon, this is a schematic for illustrativepurposes only. Fourth affordance 904 may depict a realistic rendering ofthe Moon, similar to how the Moon actually appears in the night sky.Screen 904 also includes fifth affordance 906, which illustrates thecurrent time by showing the current date, day of the week, and month. Insome embodiments, 906 indicates the current time of the day.

Device 900 receives a user input (e.g., movement 912 of the rotatableinput mechanism), and in response to receiving the user input, thedevice rotates the simulation of the Moon to display the Moon as seenfrom the Earth at a non-current time, as shown on screen 920 byaffordance 922, which represents the Moon at a non-current time, whichis indicated by updated fifth affordance 924. A non-current time may bewithin the current month or in a different month.

This is somewhat analogous to the user interaction with the simulationof the Earth described for FIG. 8. The context-specific user interfaceexemplified in FIG. 9 allows the user to access information about theappearance of the Moon (e.g., Moon phase, or which regions of the Moonmay be visible from Earth) at various times. In some embodiments, thesize of the displayed simulation of the Moon may be representative ofthe relative distance between the Earth and the Moon at the depictedcurrent or non-current time, or it may be representative of the visualsize of the Moon at the depicted current or non-current time asperceived from Earth. The device may obtain such information from, e.g.,a service or external server such as from NASA.

In some embodiments, a user may rotate the representation of the Moonand view corresponding times by swiping the touch-sensitive display. Insome embodiments, the user input may include a swipe on thetouch-sensitive display in a first swipe direction. In some embodiments,in response to receiving the user input, the simulation of the Moon asseen from the Earth is rotated in a first direction of rotation. In someembodiments, the first direction of rotation may be based at least inpart on the first swipe direction. As used herein, a rotation of theMoon may include a rotation of the Moon on its axis to depict adifferent region of the Moon (e.g., a region of the Moon not visiblefrom the Earth) and/or updating the appearance of the Moon as viewedfrom Earth at a particular time of interest, based on a rotation of therelative positions of the Moon, Earth, and Sun (e.g., updating thedisplayed lunar phase).

In some embodiments, the device receives a second user input, and inresponse to receiving the second user input, the device rotates thesimulation of the Moon as seen from the Earth in a second direction ofrotation that is different from the first direction. This user inputcould include, e.g., a swipe on the touch-sensitive display in a secondswipe direction that is different from the first swipe direction.

This allows the user to direct both the direction of rotation of theMoon, and the time indicated by the fifth affordance, in response toswiping. For example, the user may swipe in one direction to rotate theMoon in a specific direction and view the Moon at later times in themonth, and the user may swipe in another direction to rotate the Moon inan opposite direction and view the Moon at earlier times in the month.

In some embodiments, as shown in FIG. 9, a user may rotate therepresentation of the Moon and view corresponding times by rotating arotatable input mechanism. Thus, in some embodiments, the device has arotatable input mechanism (e.g., 506), and the user input may include amovement of the rotatable input mechanism in a first direction ofrotation (e.g., rotation 912). In some embodiments, in response toreceiving the user input, the simulation of the Moon as seen from theEarth is rotated in a first direction of rotation. In some embodiments,the first direction of rotation may be based at least in part on thedirection of movement of the rotatable input mechanism.

In some embodiments, the device receives a second user input, and inresponse to receiving the second user input, the device rotates thesimulation of the Moon as seen from the Earth in a second direction ofrotation that is different from the first direction. This user inputcould include, e.g., a movement of the rotatable input mechanism in asecond direction of rotation that is different from the first directionof rotation.

This allows the user to direct both the direction of rotation of theMoon, and the time indicated by the fifth affordance, in response torotating the rotatable input mechanism. For example, the user may movethe rotatable input mechanism in one direction to rotate the Moon in aspecific direction and view the Moon at later times in the month, andthe user may move the rotatable input mechanism in another direction torotate the Moon in an opposite direction and view the Moon at earliertimes in the month.

In any of the embodiments described herein, the displayed simulation ofthe Moon may indicate one or more additional lunar attributes, such asspecial moons (e.g., blue, black, or red moons, lunar eclipses, and soforth), the distance between the Moon and the Earth (as described above,e.g., for a supermoon), and/or moon wobble. In some embodiments, theadditional lunar attribute(s) may be indicated by altering theappearance of the displayed simulation of the Moon (e.g., by changingthe color, size, and/or tilt of the displayed simulation of the Moon).In some embodiments, the additional lunar attribute(s) may be indicatedby text. In some embodiments, the additional lunar attribute(s) maycorrespond to the current lunar attribute(s). In some embodiments, theadditional lunar attribute(s) may correspond to the lunar attribute(s)at the currently displayed date (e.g., if the user has rotated the Moonto view the Moon at earlier or later times in the month, as describedabove). For example, in some embodiments, while the simulation of theMoon is being rotated to depict the Moon at different times of the monthor year, the simulation of the Moon may be updated to reflect one ormore additional lunar attributes at the time currently indicated by thedisplayed simulation of the Moon.

In some embodiments, the device may display additional lunar informationin response to a user input. The additional lunar information may bedisplayed, e.g., as part of screen 902 or 920, or on a user interfacescreen that replaces screen 902 or 920 (such as a lunar informationapplication). Additional lunar information may include withoutlimitation the name of the lunar phase, the distance from the Earth tothe Moon, the time of moonrise and/or moonset (e.g., on the current dayand/or at the user's current location), and the like. In someembodiments, the additional lunar information may correspond to thecurrent lunar information (e.g., the current lunar phase, distance tothe Moon, time of moonset/moonrise, etc.). In some embodiments, theadditional lunar information may correspond to the lunar information ofthe currently displayed date, e.g., if the user has rotated the Moon toview the Moon at earlier or later times in the month, as describedabove.

For example, in some embodiments, the device may detect a user input(e.g., a user double tap on the touch-sensitive display, including afirst contact on the touch-sensitive display and a second contact on thetouch-sensitive display). In the exemplary embodiment and in response tothe user double tap, the device may determine whether the first contactand the second contact were received within a predetermined interval. Inresponse to detecting the user double tap, and in accordance with thedetermination that the first contact and the second contact werereceived within the predetermined interval, the device may displayadditional lunar information.

In some embodiments, the user interface screen, after updating thedisplay to show the simulation of the Moon, displays an affordanceindicating an earth (e.g., 910 or 928). Upon contacting the earthaffordance, the user may return to the context-specific user interfacedescribed in reference to FIG. 8. In some embodiments, the earthaffordance may be a graphical or stylized representation of an earthsuch as an icon, symbol, or a text indicating an earth. In someembodiments, the earth affordance may be a realistic rendering of theEarth.

In some embodiments, device 900 displays on the user interface screen asixth affordance representing a solar system (as depicted by affordances810, 828, 848, 908, and 926). In some embodiments, the sixth affordancemay be a graphical or stylized representation of a solar system such asan icon, symbol, or a text indicating a solar system. In someembodiments, the sixth affordance may be a realistic rendering of thesolar system.

Device 900 detects a contact on the displayed sixth affordance, and inresponse to detecting the contact, the device updates the display of theuser interface screen by displaying a seventh affordance withrepresentations of the Sun, the Earth, and one or more non-Earth planetsat their respective positions at the current time and an eighthaffordance indicating the current time. In some embodiments, updatingthe display of the user interface screen includes animating the firstaffordance representing the simulation of the first region of the Earthas illuminated by the Sun or animating the fourth affordancerepresenting a simulation of the Moon as seen from the Earth by zoomingout. This animation allows the user to recognize that the astronomicalscale and/or perspective has changed.

This transitions the user from viewing information about the currenttime within the current month using a simulation of the Moon to viewinginformation about the current time within the current year using asimulation of the solar system. Whereas the context-specific userinterface described in reference to FIG. 9 provides the usercustomizable information about lunar conditions, a context-specific userinterface that provides the user customizable information about thesolar system and relative positions of the Earth and other planet(s) isillustrated in FIG. 10.

FIG. 10 shows exemplary context-specific user interfaces that may beoperated on device 1000. Device 1000 may be device 100, 300, or 500 insome embodiments. The electronic device has a touch-sensitive display(e.g., touchscreen 504).

As described above, device 1000 is device 800 and/or device 900 with anupdated display. Device 1000 displays screen 1002, which includesseventh affordance 1004. Seventh affordance 1004 includes representationof the Sun 1006, representation of the Earth 1008, and representationsof Mercury, Venus, and Saturn (e.g., Saturn is depicted by planet 1010).1006, 1008, and 1010 are depicted at their respective positions at thecurrent date (in this example, May 25, 2014), indicated by eighthaffordance 1012. In some embodiments, eighth affordance 1012 alsoindicates the current time of day.

Optionally, in some embodiments, the solar system depicts all 8 planets.In some embodiments, the solar system depicts the four inner planets. Insome embodiments, the solar system depicts other astronomical features,such as an asteroid or asteroid belt, one or more moons of one or moreplanets (e.g., the Moon), a manmade satellite or other space probe, acomet, Pluto, and so forth.

Device 1000 receives a seventh user input (e.g., movement 1018 of therotatable input mechanism). In response, device 1000 updates the seventhaffordance to depict respective positions of the Sun, the Earth, and theone or more non-Earth planets for a non-current date. This is depictedby seventh affordance 1022 on screen 1020. Seventh affordance 1022includes representation of the Sun 1024, representation of the Earth1026, and representations of Mercury, Venus, and Saturn (e.g., Saturn isdepicted by planet 1028) at their respective positions at thenon-current date, which is Nov. 25, 2014, as depicted by eighthaffordance 1030. In some embodiments, eighth affordance 1030 alsoindicates the current time of day.

This context-specific user interface allows the user to accessinformation about the relative positions of the Earth and one or morenon-Earth planets at a non-current date, which may be within the currentyear or in a different year. In some embodiments, the Sun, the Earth,and the one or more non-Earth planets are depicted as realisticrenderings. In some embodiments, the Sun, the Earth, and the one or morenon-Earth planets are depicted as stylized or symbolic renderings.

In some embodiments, a user may rotate the representation of the solarsystem by swiping on the touch-sensitive display. Thus, in someembodiments, the user input may include a swipe on the touch-sensitivedisplay. In some embodiments, in response to detecting a swipe, theEarth and the one or more non-Earth planets are rotated about the Sun ina first direction of rotation. In some embodiments, the first directionof rotation may be based at least in part on the first swipe direction.

In some embodiments, in response to detecting a swipe on thetouch-sensitive display in a different direction, the device rotates theEarth and the one or more non-Earth planets about the Sun in a seconddirection of rotation that is different from the first direction. Thisallows the user to direct both the direction of rotation of the Earthand the one or more non-Earth planets, and the time indicated by theeighth affordance, in response to swiping. For example, the user mayswipe in one direction to rotate the Earth and the one or more non-Earthplanets in a specific direction and view the Earth and the one or morenon-Earth planets at later dates during the year (or in a differentyear), and the user may swipe in another direction to rotate the Earthand the one or more non-Earth planets in an opposite direction and viewthe Earth and the one or more non-Earth planets at earlier dates duringthe year (or in a different year).

In some embodiments, as shown in FIG. 10, a user may rotate therepresentation of the solar system by rotating a rotatable inputmechanism (e.g., 506). In these embodiments, the user input may includea movement of the rotatable input mechanism in a first direction ofrotation (e.g., movement 1018). In some embodiments, in response toreceiving the user input, the Earth and the one or more non-Earthplanets are rotated about the Sun in a first direction of rotation. Insome embodiments, the first direction of rotation may be based at leastin part on the direction of movement of the rotatable input mechanism.

In some embodiments, the device receives a second user input, and inresponse to receiving the second user input, the device rotates theEarth and the one or more non-Earth planets about the Sun in a seconddirection of rotation that is different from the first direction. Thisuser input could include, e.g., a movement of the rotatable inputmechanism in a second direction of rotation that is different from thefirst direction of rotation.

This allows the user to direct both the direction of rotation of theEarth and the one or more non-Earth planets, and the time indicated bythe eighth affordance, in response to rotating the rotatable inputmechanism. For example, the user may move the rotatable input mechanismin one direction to rotate the Earth and the one or more non-Earthplanets in a specific direction and view the Earth and the one or morenon-Earth planets at later times in the year, and the user may move therotatable input mechanism in another direction to rotate the Earth andthe one or more non-Earth planets in an opposite direction and view theEarth and the one or more non-Earth planets at earlier times in theyear.

In some embodiments, the representation of the Earth may further includea representation of the orbit of the Earth around the Sun. In someembodiments, the representation of the one or more non-Earth planets mayfurther include a representation of the orbit of the one or morenon-Earth planets around the Sun. The representation of an orbit may bea graphical representation, such as a line or ring. In some embodiments,the representation of the orbit may be stylized. In some embodiments,the representation of the orbit may be based on the actual dimensions ofthe planet's orbit around the Sun.

In some embodiments, the user may contact the touch-sensitive display ata location associated with the representation of the Earth or the one ormore non-Earth planets. For example, the contact may be at or near thedisplayed representation of the planet itself, or the contact may be ator near the displayed representation of the planet's orbit. In someembodiments, the device may determine the selected planet based on adetermination of the displayed representation of a planet or thedisplayed representation of a planet's orbit nearest to the location ofthe contact. In some embodiments, the contact may be a press andhold-type contact on the display. Upon detecting the contact, the devicemay visually distinguish the representation of the selected planetand/or the representation of the selected planet's orbit (e.g., byaltering the color and/or brightness of the displayed planet and/ororbit, by displaying an outline or other visual demarcation of theplanet and/or orbit, by animation the planet and/or orbit, etc.). Insome embodiments, while continuing to receive the contact, the devicemay determine whether the duration of the contact exceeds apredetermined threshold and, in accordance with a determination that thecontact exceeds the predetermined threshold, the device may visuallydistinguish the representation of the selected planet and/or therepresentation of the selected planet's orbit. When the user lets go ofthe contact, the device may display information about the selectedplanet. Such information may include, without limitation, the size ofthe planet, the distance (e.g., current distance, average distance,etc.) between the planet and the Sun, the distance (e.g., currentdistance, average distance, etc.) between the planet and the Earth (ifthe selected planet is not the Earth), a time and/or location in the skywhen the planet will be visible from the Earth (if the selected planetis not the Earth), a temperature on the surface of the planet, thenumber of moons orbiting the planet, the number and/or identity of anyspacecraft currently orbiting or near the planet, a description of theplanet (e.g., whether the planet is terrestrial or gas, the date ofdiscovery of the planet, information about the planet's name, and thelike), a time (past, present, or future) of a particular alignment ofthe planet with another object in the solar system, and so forth.

After viewing the information about the planet, the user may wish todismiss the information or view information about another planet. Insome embodiments, the user may tap to dismiss the information or swipeto select another planet. For example, a swipe in a first direction mayselect the next planet whose orbit is farther from the Sun, relative tothe previous planet, and a swipe in the opposite direction may selectthe next planet whose orbit is nearer to the sun, relative to theprevious planet. In some embodiments, after displaying the informationabout the Earth or the one or more non-Earth planets associated with thecontact, the device may receive a user input and determine whether theuser input represents a tap or a swipe on the touch-sensitive display(e.g., by using contact/motion module 130 to detect the user gesture).In accordance with a determination that the user input represents a tap,the device may remove the displayed information about the planet. Inaccordance with a determination that the user input represents a swipe,the device may replace the displayed information about the planet withinformation about a second planet different from the first planet (e.g.,a planet not associated with the user contact).

In some embodiments, the user interface screen, after updating thedisplay to show the simulation of the solar system, displays anaffordance indicating a moon (e.g., 1016 or 1034) and/or an affordanceindicating an earth (e.g., 1014 or 1032). In some embodiments, the moonand/or the earth affordance may be a graphical or stylizedrepresentation of an earth or moon such as an icon, symbol, or a text.In some embodiments, the moon and/or the earth affordance may be arealistic rendering of the Moon or the Earth. Upon contacting the earthaffordance, the user may return to the context-specific user interfacedescribed in reference to FIG. 8. Upon contacting the moon affordance,the user may return to the context-specific user interface described inreference to FIG. 9.

In some embodiments of any of the context specific-user interfacesillustrated in FIGS. 8-10, a user may move (e.g., rotate) a rotatableinput mechanism to scroll a displayed indication of time forward orbackward in time. It is to be appreciated that such a feature may beapplied to any of the context-specific user interfaces described herein;however, for ease of explanation, this feature may be described inreference to FIGS. 8-10. Any model for mapping a movement of a rotatableinput mechanism to the distance or speed of scrolling may be used, suchas those described in U.S. patent application Ser. No. 14/476,700,“Crown Input for a Wearable Electronic Device,” filed Sep. 3, 2014,which is hereby incorporated by reference in its entirety. For example,acceleration, velocity, or the like may be used to determine the amountof speed of scaling of the displayed indication of time.

In some embodiments, a user may move the rotatable input mechanism toscroll the indication(s) of time displayed on screen 802, 820, and/or840. In response to detecting the movement of the rotatable inputmechanism (e.g., movement 830), the device may update the displayedrepresentation of the Earth, for example by simulating a rotation of theEarth, to display the Earth as illuminated by the Sun at a differenttime of day (compare 822 and 842). In some embodiments, the device mayupdate the displayed indication of time to show a different time(compare 824 and 844). Similarly, as shown in FIG. 9, in response todetecting the movement of the rotatable input mechanism (e.g., movement912), the device may update the displayed simulation of the Moon todisplay a different moon phase at a different time of month (compare,e.g., 904 and 922), and/or update the displayed indication of time toshow a different time (compare, e.g., 906 and 924). Similarly, as shownin FIG. 10, in response to detecting the movement of the rotatable inputmechanism (e.g., movement 1018), the device may update the displayedpositions of the Earth and the one or more non-Earth planets to displaydifferent positions relative to the Sun at different times of year(compare, e.g., 1008 and 1010 to 1026 and 1028), and/or update thedisplayed indication of time to show a different time (compare, e.g.,1012 and 1030). In some embodiments, the representations of the Earth,the Moon, and/or the positions of the Earth and the one or morenon-Earth planets may be rotated in a direction based on the directionof movement of the rotatable input mechanism. In some embodiments, therepresentations of the Earth, the Moon, and/or the positions of theEarth and the one or more non-Earth planets may be rotated at a ratebased on the rate and/or amount of movement of the rotatable inputmechanism, e.g., according to any of the models referenced above. It isto be appreciated that, depending on the displayed context-specific userinterface, movement of the rotatable input mechanism may cause thedisplayed indication of time to be updated at different timescales. Forexample, the same degree and/or rate of rotation may cause thecontext-specific user interface shown in FIG. 8 to update by an hour,whereas the context-specific user interface shown in FIG. 9 may updateby a day or week, or the context-specific user interface shown in FIG.10 may update by a month or year.

In some embodiments of any of the context specific-user interfacesillustrated in FIGS. 8-10, the device may indicate other global orastronomical features or objects, such as the real-time position of theInternational Space Station, as described above. In some embodiments, auser may tap on the display (e.g., at a location corresponding tospace), and in response to detecting the tap, the device may providefurther information on other global or astronomical features or objects,e.g., the number of people currently in space, the number and/or name(s)of spacecraft currently in space, etc.

FIG. 11A shows exemplary context-specific user interfaces that may beoperated on device 1100. Device 1100 may be device 100, 300, or 500 insome embodiments. The electronic device has a touch-sensitive display(e.g., touchscreen 504).

A user may wish to view the time of day in the context of daytime andnighttime hours. For example, a user may wish to know the time of dawnor dusk, or access a simple, visual indication of how much time is leftbefore sunset.

As shown in FIG. 11A, device 1100 displays user interface screen 1102.User interface screen 1102 has two portions: first portion 1104indicating daytime, and second portion 1106 indicating nighttime. Screen1102 also displays a user interface object representing a sinusoidalwave 1108. Sinusoidal wave 1108 may represent the general appearance ofa sinusoidal wave without mathematical accuracy or precision.Importantly, however, sinusoidal wave 1108 has a period of approximatelya day and indicates the path of the Sun through the day. As shown inFIG. 11A, the troughs of 1108 represent solar midnight (corresponding totwo solar midnights 24 hours apart), and the peak of 1108 representssolar noon for the day. Also displayed on screen 1102 is firstaffordance 1110, which is displayed at a position along sinusoidal wave1108 at a position that indicates the current time of day. Screen 1102also displays horizon line 1112, an optional feature which divides thedaytime and nighttime portions of the display. As shown, horizon line1112 intersects sinusoidal wave 1108 at two points, representing sunriseand sunset. Finally, screen 1102 displays second affordance 1114, whichindicates the current time of day.

Through the course of the day, 1114 displays the current time (in thisexample, 5:30 am), and first affordance 1110 tracks along the sinusoidalwave. When 1110 is in daytime portion 1104, the current time is duringdaytime. When 1110 is in nighttime portion 1106, the current time is innighttime. At 5:30 am, it is just before dawn, as first affordance 1110is still in the nighttime portion of screen 1102. The features of thiscontext-specific user interface provide the user a simple and intuitiveway to track the current time and understand how long it is until, forexample, sunset, or sunrise. In some embodiments, the affordancerepresenting the sun appears hollow (e.g., like a ring) when at aposition fully within the nighttime portion (e.g., 1106) of the display,as shown by first affordance 1110. This further reinforces to the userthat it is currently before dawn.

For example, screen 1120 shows a second time of day and includes firstaffordance 1122, sinusoidal wave 1124, and second affordance 1126. Asindicated by second affordance 1126, it is now sunrise at 7:00 am. Theposition of first affordance 1122 along wave 1124 is between the firstportion and the second portion, indicating the transition from nighttimeto daytime. This is further depicted on screen 1120 by positioningaffordance 1122 on line 1128, which separates the two portions of thedisplay. This is yet further indicated by the appearance of affordance1122 itself, which, optionally, may be half-filled when the affordanceis at a position intersecting the first and second portions of thedisplay.

Screen 1130 shows a third time of day and includes first affordance1132, sinusoidal wave 1134, and second affordance 1136. As indicated bysecond affordance 1136, it is now 2:00 pm. The position of firstaffordance 1132 along wave 1134 is within the first portion of thedisplay, indicating daytime. This is further depicted by the appearanceof affordance 1132 itself, which, optionally, may be filled when theaffordance is at a position fully within the first portion.

In some embodiments, the color of the first and/or the second portion(s)may indicate daytime (e.g., with a warm or bright color) or nighttime(e.g., with a dark or cool color). In some embodiments, the first andsecond portions may be the same color, which may be representative ofthe current light conditions. In these embodiments, the user may stillbe able to tell the current light conditions through the sinusoidalwave, optional horizon line, and/or optional appearance of the sunaffordance (e.g., filled, half-filled, or hollow). In some embodiments,the sinusoidal wave may include two or more colors, and these colors mayindicate the daytime and nighttime portions (e.g., parts of the wave inthe daytime portion may be one color, and parts of the wave in thenighttime portion may be another). Moreover, the two portions may be ofany shape (not limited to rectangular). For example, the daytime portionmay appear as an illuminated circle that encompasses the sinusoidalwave, with the nighttime portion appearing all around the circle.

In some embodiments, device 1100 may have a location sensor (e.g., GPSsensor 532 and/or GPS module 135). In these embodiments, device 1100 mayobtain a current location of the device from the location sensor andindicate daytime and nighttime hours at the current location at thecurrent time through the ratio of the displayed first and secondportions. That is to say, the size of the daytime and nighttime portionsof the display may be adjusted, relative to daytime hours at the currentlocation and date. As an illustrative example, if the current locationis near the Arctic Circle during summer, the daytime portion may includeall or nearly all of the screen, such that all or nearly all of thedisplayed sinusoidal wave is within the daytime portion. As anotherexample, if the user were to travel latitudinally across the globe, theposition of affordance 1110, 1122, or 1132 (for example) would notchange, but the ratio of daytime:nighttime portions and relative amountof the sinusoidal wave within each would be adjusted to reflect thecurrent location. This provides a more realistic depiction of the timeof day to the user, thus enhancing the user interface.

In some embodiments, the amplitude of the displayed sinusoidal wave isbased on the height of the Sun relative to the horizon at the currentlocation and current time. For example, the wave may flatten orotherwise decrease in amplitude to reflect the sun having a lower paththrough the sky at the location and current day (e.g., in locations moreproximal to the poles in winter).

Attention is now directed to FIG. 11B, which illustrates an example ofthis context-specific user interface that provides a user-interactablefeature to view additional day/night information. FIG. 11B shows userinterface screen 1140 that can be displayed on device 1100. Screen 1140includes first affordance 1142, which represents the position of the sunat the current time along sinusoidal wave 1144. Screen 1140 alsodisplays second affordance 1146, which also indicates the current time(10:09 am). Device 1100 receives a user contact at displayed firstaffordance 1142, shown by touch 1148.

As detected by device 1100, the user touches first affordance 1142 anddrags the affordance to a second position along the sinusoidal wave in acontinuous gesture (as indicated by touch 1166). In response, as shownon screen 1160, device 1100 displays first affordance 1162 at the secondposition along sinusoidal wave 1164. Device 1100 also updates the secondaffordance 1168 to indicate a non-current time. This new time (12:09)corresponds to the time of day indicated by the second position ofaffordance 1162. Thus, the user is able to view the time of dayrepresented by any position along the sinusoidal wave by simply movingaffordance 1148 and/or 1166.

It is to be noted that the movement of the contact may begin and end atpositions on the sinusoidal wave, but the movement itself need notprecisely track the sinusoidal wave. That is, the user is not requiredto track the contact precisely along the sinusoidal wave. The device maysimply receive a user contact at the displayed first affordance, and,while continuing to receive the user contact, detect a movement of thecontact from the first position to a second position without a break inthe user contact on the touch-sensitive display (e.g., the user does notlift their finger off the touch-sensitive display).

In response to detecting the contact at the second position, the devicemay translate the first affordance on-screen to the second positionwhile tracking the sinusoidal wave. Thus, while the user contact doesnot need to track the sinusoidal wave, the device nonetheless translatesthe first affordance from the first position to the second position bytracking the first affordance along the sinusoidal wave. In someembodiments, the device may continuously update the time, as indicatedby the second affordance. Alternatively, the device may update the timeindicated by the second affordance when the continuous contact has cometo rest at the second position. In alternative embodiment, afterdetecting the contact at the first position, the device may translatethe first affordance on-screen to the second position on the sinusoidalwave in response to a rotation of a rotatable input mechanism.

FIG. 11B illustrates optional features of this context-specific userinterface. As shown on screen 1140, in response to receiving user touch1148 at affordance 1142, device 1100 displays affordances 1150 and 1152,which depict sunrise and sunset, respectively. Affordances 1150 and 1152are displayed along wave 1144 at the two points where the waveintersects the boundary between the first portion indicating daytime andthe second portion indicating nighttime. This boundary is demarcated onscreen 1140 with optional horizon line 1154. When horizon line 1154 isdisplayed, affordances 1150 and 1152 are displayed at the two pointswhere line 1154 intersects wave 1144. In some embodiments, affordances1150 and 1152 may further include a numerical display of sunrise andsunset times, respectively, for the current day. In some embodiments,these affordances are also displayed while device 1100 receives usercontact at the second position.

Also displayed on screen 1140 in response to receiving user touch 1148at affordance 1142 are affordances 1156 and 1158. Affordances 1156 and1158 are displayed along wave 1144 at positions corresponding to dawnand dusk, respectively. In some embodiments, these affordances are alsodisplayed while device 1100 receives user contact at the secondposition. These displayed affordances indicate to the user when firstand last light will occur, allowing the user to visually gauge when theywill occur, or how long ago they occurred, by the distance fromaffordance 1142. In some embodiments, the time of dawn may beastronomical dawn, nautical dawn, or civil dawn. In some embodiments,the time of dusk may be astronomical dusk, nautical dusk, or civil dusk.

In some embodiments, device 1100 detects a contact at the displayedfirst affordance, a movement of the contact, and a break in contact. Inresponse to detecting the break in contact, the device may translate thefirst affordance back to the position indicating the current time andupdate the second affordance to indicate the current time. This allowsthe user to drag the affordance to a position of interest, view theindicated time for that position, and by releasing the contact, “snapback” to the current position.

FIG. 11C illustrates further optional features of this context-specificuser interface. In some embodiments, particularly when the userinterface screen is displayed on a reduced-size display, it may bedesirable to display each of the elements as large as possible forvisibility. Screen 1170 displays first affordance 1172, sinusoidal wave1174, and second affordance 1176. As shown, affordance 1176 intersectswave 1174. When the current time reaches 2:00, as shown on screen 1180,the position of affordance 1182 indicating 2:00 along wave 1184intersects with the position of the second affordance. Device 1100 maydetermine whether the position of the first affordance intersects withthe second affordance (e.g., a position that would overlap with, beobscured by, or otherwise appear close to the second affordance). Inresponse to a determination that the affordances intersect, the devicemay display the second affordance at another position on the displaythat does not intersect. As illustrated on screen 1180, the position ofaffordance 1186 is different from that of 1176, because the relativeposition of 1176 on the screen would intersect with first affordance1182. This accommodation allows the device to display a richlyinformative screen without visual interference between displayedelements.

The user may also contact the touch-sensitive display with touch 1188 onscreen 1180. This contact may be, for example, at any position on thedisplay besides the position of the first affordance representing thesun at the current time. In response to detecting the contact, device1100 displays screen 1190, which includes sunrise time 1192, sunset time1194, and affordance 1196, which provides a non-textual indication ofdaytime and nighttime. This allows the user to access sunrise and sunsettimes from any user interface screen.

The user may also set a reminder for a time of day through thiscontext-specific user interface. For example, if the device has arotatable input mechanism (e.g., 506), the user may rotate the rotatableinput mechanism to set the reminder. In response to detecting a movementof the rotatable input mechanism, the device may translate the firstaffordance to a third position indicating a non-current time of day. Theuser may contact the first affordance displayed at the third position,and in response to detecting the contact, the device may set a userreminder for the indicated time of day.

For example, the device may display another affordance representing auser prompt to set an alert for the indicated time of day. The remindercould be a visual alert. In this example, the device may display avisual alert that is displayed when the time of day is approaching.Alternatively, the device may display at any time a visual affordancethat shows the third position along the sinusoidal wave to help the userunderstand how far the indicated time of day is from the current time.In some embodiments, the user reminder could include an audio alert thataudibly notifies the user when the indicated time of day has arrived orwill arrive shortly. In some embodiments, the user reminder couldinclude a haptic alert. The device may create a haptic signal to theuser when the indicated time of day is approaching (e.g., using hapticfeedback module 133 and tactile output generator 167).

These features allow the user to further customize this context-specificuser interface. It is to be appreciated that this feature does notcreate a specific alert at a time and date; rather, it allows the userto set a generic alert for a time of day that is not tied to a specificdate. For example, a user may notice a certain lighting effect, such assunlight through a window in their house, and wish to set a reminder sothat they can view this effect at the time of day when it occurs. Withinthe context of daytime/nighttime information, this allows the user tocustomize the user interface to include not only sunrise, sunset, dawn,dusk, and so forth, but also a time of day that they wish to designate.

FIG. 12 shows exemplary context-specific user interfaces that may beoperated on device 1200. Device 1200 may be device 100, 300, or 500 insome embodiments. In some embodiments, the electronic device has atouch-sensitive display (e.g., touchscreen 504).

A user may wish to view a certain background image on the user interfacescreen while retaining as much of the original image as possible.Therefore, it may be advantageous to provide a context-specific userinterface that displays the time and/or date not simply as interfaceobjects displayed over the image, but rather interface objects thatappear to arise from the image itself, thereby maximizing the user'sview of the image while still providing visible indications of the timeand date. This may be particularly true if the user interface isdisplayed on a reduced-size display.

As shown in FIG. 12, device 1200 is displaying user interface screen1202, which includes background 1204. Background 1204 is based on animage of a beach. In some embodiments, the image may be a photo.

As used here, consistent with its accepted meaning in the art, thephrase “background” refers to the background of a user interface screenthat is visually distinguishable from text and user interface objectsalso displayed in the user interface screen. Basing a background on animage simply means displaying the image as a background of a displayedscreen. In some cases, the image and the background may be identical. Inother cases, displaying the image as a background may involve modifyingone or more aspects of the image to fit on the display, such as imagesize, image cropping, image resolution, and so forth.

Screen 1202 also includes user interface objects 1206 and 1208. 1206indicates a date (the 23^(rd)), whereas 1208 indicates a time of day(10:09). In some embodiments, the device may indicate the current dateand/or the current time of day.

Displayed background 1204 includes a plurality of pixels. A subset ofthese pixels is modified in appearance relative to the image such thatthe subset comes to represent one or more of user interface object 1206and user interface object 1208. That is to say, at least one of theseuser interface objects is displayed by modifying the background. Forexample, the subset of pixels may be modified by changing color and/orintensity.

In some embodiments, the subset of the pixels may be modified by colorblending. In some embodiments, the subset of the pixels may be modifiedby color blurring. In some embodiments, the subset of the pixels may bemodified by applying a gradient. Importantly, these examples illustratethat the appearance of the subset of the pixels may be influenced byboth the background image at the position of the user interfaceobject(s) and the user interface object(s) themselves. This allows theuser to view the image more clearly (since the user interface object(s)are not simply displayed on top of and obstructing the image), whilealso maintaining the legibility of the user interface object(s).

In some embodiments, one of user interface objects 1206 and 1208 isdisplayed by modifying the background, and the other is displayedindependent of the background (e.g., a set color and/or intensity notproduced by modifying the background pixel subset). In theseembodiments, the device may receive data representing a background colorat the position of the displayed user interface object (e.g., 1206 or1208), and the color of the displayed user interface object may bedifferent from this background color (e.g., a different color and/orintensity). For example, a background color at the position of thedisplayed user interface object may include the most prevalent color atthat position. This feature ensures that, if one of the user interfaceobjects is a preset color, it will be displayed legibly on thebackground, no matter the appearance of the background.

In some embodiments, the image on which the background is based may bestored on device 1200.

In other embodiments, the image on which the background is based may bestored on an external device that is coupled to device 1200 via wirelesscommunication (e.g., Wi-Fi, Bluetooth™, near field communication(“NFC”), or any of the other cellular and/or other wirelesscommunication techniques described herein). In these embodiments, beforedisplaying screen 1202, device 1200 may receive (via wirelesscommunication) data representing the background from the externaldevice. Using these data, device 1200 may then display the background.

Optionally, when the image is stored on an external device, device 1200may display a background based on the current background of the externaldevice. For example, the device may receive (via wireless communication)data representing a current background from the external device anddisplay a user interface screen that includes a background correspondingwith the current background of the external devices. The device thenmodifies a subset of the pixels of the background from the externaldevice to represent one or more of a user interface object indicating adate and a user interface object indicating a time of day. In someembodiments, device 1200 may further alter the background from theexternal device, for example, by changing one or more of the image size,image cropping, image resolution, and the like, particularly if theexternal device and device 1200 have different display dimensions and/orresolutions.

Returning to FIG. 12, a user may wish to select an image from a folderof images to serve as the background. Thus, device 1200 may access afolder that includes two or more images (e.g., the images shown onscreens 1202 and 1210), select a first image, and display a userinterface screen that includes a background based on the first image(e.g., background 1204). As described above, this background includes asubset of pixels that are modified in appearance relative to the imageto represent one or more of a user interface object indicating a date(e.g., 1206) and a user interface object indicating a time (e.g., 1208).

Optionally, as shown in FIG. 12, after displaying screen 1202, device1200 may receive data representing a user input. In response, device1200 obtains data representing background 1204, select a second imagefrom the folder that is different from the first image, and displayscreen 1210, which includes background 1212 based on the second image.As shown in FIG. 12, backgrounds 1204 and 1212 are based on differentimages: a beach scene and a mountain scene, respectively. This featureensures that, when the user decides to change the displayed background,the device displays a different image, compared to the image displayedbefore the user input.

As shown on FIG. 12, screen 1210 also includes user interface object1214 indicating a date and user interface object 1216 indicating a timeof day. At least one of these user interface objects is displayed bymodifying a subset of pixels of background 1212 at the position of thedisplayed user interface object(s), as described above. This subset maybe modified in any of the ways described above, such as color blending,blurring, gradient, etc. In some embodiments, one of the user interfaceobjects may be a color independent of the background, and device 1200may modify this color to adapt to the background, as set forth above.The image on which the background is based may be stored on device 1200or on an external device, as described above.

A variety of user inputs may serve as the user input to change thebackground. In some embodiments, the user input may be a touch on thedisplay, a rotation of a rotatable input mechanism, a depression of adepressible and rotatable input mechanism, or a swipe on the display. Insome embodiments, the user input may be a user movement of theelectronic device (e.g., a movement of the device such as raising of theuser's wrist, if the device is wearable, or other movement indicativethat the user is viewing the display). Advantageously, this featureenables the device to display a different image each time the display isviewed, thereby providing the user with a customized display at eachviewing and enhancing the user interaction with the device. As describedabove, a user movement of the device could be detected, for example, byusing an accelerometer (e.g., 534), a gyroscope (e.g., 536), a motionsensor (e.g., 538), and/or a combination thereof.

In some embodiments, the user may choose to exclude an image from thefolder so that it is no longer selected as a background. In theseexamples, the device may receive data representing a user prohibition ofan image from the folder. Such a prohibition may be received through theuser interface shown in FIG. 12, or it may be received through thefolder containing the two or more images (e.g., the folder may include afeature that allows the user to select more images, drag images into thefolder, delete images from the folder, and/or prohibit an image for useas a background). In response to receiving the data, the device mayprevent the display of the image as a background in response to futureuser input.

FIG. 13A shows exemplary context-specific user interfaces that may beoperated on device 1300. Device 1300 may be device 100, 300, or 500 insome embodiments. The electronic device has a touch-sensitive display(e.g., touchscreen 504).

A user may wish to view a displayed animation on an electronic device inresponse to an input. Because a user may look at an electronic devicemany times per day, particularly if the user relies on the device fortimekeeping, it may be advantageous to provide the user a differentexperience each time the display is viewed. This keeps the userinterested and engaged with the electronic device.

As shown in FIG. 13A, device 1300 displays user interface screen 1302 inresponse to detecting user input 1304 at 10:09. Screen 1302 includesuser interface object 1306, which indicates the time, as well as userinterface object 1308, which depicts a butterfly. After displayingscreen 1302, device 1300 animates butterfly 1308 by sequentiallydisplaying three animated sequences that are all different from eachother. The first animated sequence is shown by butterfly 1308, whichdepicts the butterfly opening its wings. Next, screen 1310 displays thesecond animated sequence, which depicts butterfly 1314 flying from rightto left on the display. Note that screen 1310 also displays userinterface object 1312, which indicates the time. Finally, screen 1320displays the third animated sequence, which depicts butterfly 1324closing its wings. Screen 1320 again displays user interface object 1322indicating the time.

Later in the day, as shown in FIG. 13B, device 1330 detects a seconduser input 1332. In response, device 1300 accesses data representing thepreviously displayed animated sequence (i.e., the sequence shown bybutterfly 1314). Device 1300 displays screen 1330. Screen 1330 includesuser interface object 1334, which indicates the time is now 2:09, anduser interface object 1336, which depicts a butterfly.

Device 1300 then animates butterfly 1336 by sequentially displayingthree animated sequences. Butterfly 1336 on screen 1330 is animatedusing the same sequence as butterfly 1308 on screen 1302, showing thebutterfly opening its wings. Next, screen 1340 shows butterfly 1334,which is animated to fly from left to right on the display. The animatedsequence of butterfly 1334 is different from the animated sequence ofbutterfly 1314 on screen 1310 (data representing the sequence ofbutterfly 1314 had previously been accessed). This ensures that the userwill view a different animation, as compared to the last user input.This makes the animation appear more realistic and/or engaging to theuser, as this variation imparts a more random, lifelike quality to theanimated user interface object.

Finally, screen 1350 shows butterfly 1354, which is animated using thesame sequence (a butterfly closing its wings) as butterfly 1324 onscreen 1320. Screens 1340 and 1350 also include user interface objects1342 and 1342, respectively, which indicate the time.

FIGS. 13A and 13B show two butterflies (1336 and 1308) that aredisplayed in response to user inputs. Butterfly 1336 is related to 1308,but it need not be identical. In some embodiments, user interface object1336 may be the same as user interface object 1308. In otherembodiments, user interface object 1336 may be an object related, butnot identical, user interface object 1308. For example, these userinterface objects may be animals of the same general type but withdifferent appearances (e.g., different colors, different postures,different species, and so forth).

The animated user interface object may be an animal, such as a butterflyor jellyfish, or it may be a plant, like a flower. In some embodiments,it may be a non-living object, single-celled organism, cartoon, human,and so forth. This context-specific user interface is not limited by theparticular animated user interface object. The animated sequences may bespecific to the displayed objects. For example, a jellyfish may swimacross the screen in various directions, a flower may open, close, or beblown about the wind, and so on.

As illustrated by comparing butterfly 1308 to butterfly 1324, orbutterfly 1336 to butterfly 1354, the third animated sequence may bebased on a reverse of the first animated sequence. For example, if thefirst sequence depicts a butterfly opening its wings, the third sequencemay depict a butterfly closing its wings. Since these sequences bookendthe full animated sequence, this feature imparts a cohesive feel to theentire sequence. In some embodiments, the state of the user interfaceobject at the beginning of the first animated sequence (e.g., butterfly1308 has closed wings, which are then animated to open) corresponds withthe state of the user interface object at the end of the third animatedsequence (e.g., butterfly 1324 is animated to end on closed wings),thereby providing the user with the impression of one seamlessanimation.

A variety of user inputs may serve as the user input to display thescreens exemplified in FIG. 13. In some embodiments, the user input maybe a touch on the display, a rotation of a rotatable input mechanism, adepression of a depressible and rotatable input mechanism, or a swipe onthe display. In some embodiments, the user input may be a user movementof the electronic device (e.g., a movement of the device such as raisingof the user's wrist, if the device is wearable, or other movementindicative that the user is viewing the display). Advantageously, thisfeature enables the device to seemingly display a different animationeach time the display is viewed.

In some embodiments, the user interface object displayed in response touser input may be the same after each input. In some embodiments, theuser interface object could be different each time. For example, a userinterface object may be reflected (e.g., about a horizontal and/or avertical axis), flipped, and/or rotated to create a new user interfaceobject. This is a source of variety for the displayed user interfaceobject and the animated sequences. For example, rotating a single objecthorizontally, vertically, and horizontally and vertically creates fournew objects, which when coupled with an animation that directs themovement of the object creates even more variations. These aspects addcombinatorial possibilities which greatly increase the number ofavailable animations for a single object, thus reducing the number ofpre-programmed animated sequences. It also helps animate objects withfewer intrinsic features and/or movements, such as a jellyfish.

The user may also change the displayed user interface object. Forexample, device 1300 may detect a contact on the touch-sensitivedisplay, and in response, device 1300 may substitute the displayed userinterface object with a second user interface object. This second userinterface object may be related to the first (e.g., the user couldselect an orange butterfly if the previous one was blue).

In some embodiments, as shown in FIGS. 13A and 13B, the user interfaceobject indicating time may be a representation of a digital clock withnumerical indications of an hour and a minute (see, e.g., objects 1306,1312, 1322, 1334, 1342, and 1352). In some embodiments, the userinterface object may display the current time in response to user input.

FIG. 14A shows exemplary context-specific user interfaces that may beoperated on device 1400. Device 1400 may be device 100, 300, or 500 insome embodiments. The electronic device has a touch-sensitive display(e.g., touchscreen 504).

A user may wish to keep time with an interactive clock face. Forexample, a user may wish to view an animation with each viewing of thedisplay, or view a clock face that changes color, to keep theinteraction with the device interesting. A user may wish to customizethe clock face with a personalized complication, like a monogram, or apersonalized widget for displaying application data.

As shown in FIG. 14A, device 1400 has display 1402 turned off. Inresponse to detecting a user movement of device 1400 (e.g., motion1404), device 1400 displays an animated reveal of a clock face. Onscreen 1410, device 1400 displays clock face outline 1412, which isanimated as if being filled in or drawn in a clockwise manner. On screen1420, device 1400 displays full clock face outline 1422 and hour handand minute hand 1424. On screen 1430, device 1400 displays full clockface outline 1432, hour hand and minute hand 1434, and hour indications1436 and 1438 (indicating the 12 o'clock and 1 o'clock hours,respectively). These hour indications are progressively displayed in aclockwise direction, as shown by comparing screens 1430 and 1440.

On screen 1440, device 1400 displays clock face outline 1442, hour andminute hand 1444, and twelve hour indications, as represented by 12o'clock indication 1446. On screen 1450, device 1400 displays clock faceoutline 1452, hour and minute hand 1454, twelve hour indications (asrepresented by 12 o'clock indication 1456), minute indications 1458, andmonogram 1460, which is described in greater detail below. Therefore, asexemplified in FIG. 14, the clock face is animated to progressivelyreveal its features.

Two types of hour indications are depicted in FIG. 14A: numerical hourindications (e.g., 3, 6, 9, and 12, as indicated by hour indications1436, 1446, and 1456) and symbolic hour indications (e.g., the tickmarks displayed between the numerical indications on screens 1440 and1450). Either type of indication may be used, alone or in combination.Any type of symbol may be used as an hour indications; the positionaround the clock face, rather than the symbol itself, conveys to theuser which hour is indicated. The numbers of hour indications and/orminute indications (or lack thereof) may further be customized by theuser, which will be explained in greater detail below.

FIG. 14A shows that one or more hour indications may be progressivelydisplayed in a clockwise manner (e.g., they may appear sequentially in aclockwise direction, as depicted on screens 1430 and 1440). Similarly,the clock outline may optionally appear in a clockwise direction. Thishelps to orient the user. Optionally, the minute indications may appearprogressively in a clockwise manner. The hour hand and the minute hand(and, optionally, a seconds hand) may be animated as well, such asradially (e.g., starting from the center of the clock face and appearingto extend outward towards the outline). In some embodiments, the hourand minute hand appear first, followed by the hour indications, then theminute indications. In some embodiments, the clock face shows currenttime.

In some embodiments, the clock face may include a color. Features suchas the background of the clock face, clock face outline, seconds hand,hour indication(s), minute indication(s), hour hand, minute hand, and soforth may be displayed in any color. In some embodiments, device 1400updates a color displayed on the clock face over time by continuouslychanging the color, so that the user perceives time passing throughcolor change. This color may be, e.g., a background color, the color ofthe clock face itself, and/or the color of the seconds hand (e.g., theentire seconds hand, or a portion of the seconds hand, such as apointer, dot, or other optional feature). As an illustrative example,the color may cycle through a gradient of colors, with the full cyclelasting a minute, an hour, a day, etc.

In some embodiments, device 1400 may detect a user movement of thedevice. As described above, a user movement of the device could bedetected, for example, by using an accelerometer (e.g., 534), agyroscope (e.g., 536), a motion sensor (e.g., 538), and/or a combinationthereof. A user movement of the electronic device could includemovements such as a movement of the device such as raising of the user'swrist, if the device is wearable, or other movement indicative that theuser is viewing the display. In response to detecting the user movement,device 1400 may display a different color (e.g., a background color, thecolor of the clock face itself, and/or the color of the seconds hand).In some embodiments, this feature may be used to allow the user tochange a static color displayed on the clock face. In other embodiments,this feature may be used to allow the user to change a continuouslychanging color, as exemplified above.

In some embodiments, device 1400 may display a complication on the clockface (e.g., within the clock face itself, or adjacent to the clock faceon the display). As used here, consistent with its accepted meaning inart, a complication refers to any clock face feature other than thoseused to indicate the hours and minutes of a time (e.g., clock hands orhour/minute indications). For example, an affordance may be displayed asa clock face. As will be described in greater detail below, theaffordance may represent an application, and in response to detecting acontact on the affordance, device 1400 may launch the applicationrepresented by the affordance.

Returning now to FIG. 14A, in some embodiments, a monogram may bedisplayed as a complication. Screen 1450 shows monogram affordance 1460displayed as a clock face complication. Device 1400 may receive datarepresenting a name, and in response to receiving the data, generate amonogram and display the monogram as affordance 1460 (in this example,“MJ”). Device 1400 may receive this data from one or more sources, suchas a saved contact entry, a V-card, an image containing a monogram(e.g., an image taken or uploaded by a user), and so forth. In someembodiments, device 1400 has a user interface for monogram editing,which may be a feature of the user interface described in FIG. 14, aseparate user interface on device 1400, or a user interface on anexternal device in wireless communication with device 1400. It is to beappreciated that these aspects (e.g., complications, monograms, and/orcolors) may also be applied to any of the other context-specific userinterfaces described herein. These features provide customizableelements a user may wish to include to personalize one or more clockfaces, thereby improving the user interface by enhancing userinteractability.

FIG. 14B shows exemplary user interface screen 14602 that device 14000can display on its display. In some embodiments, device 14000 may be oneor more of devices 100 (FIG. 1), 300 (FIG. 3), and/or 500 (FIG. 5). Theelectronic device has a touch-sensitive display (e.g., touchscreen 504).

Users rely on personal electronic devices to keep time throughout theday. It is becoming increasingly desirable to present the user withinteractive user interfaces that promote user interaction with apersonal electronic device. Indicating the time through acharacter-based user interface may enhance a user's interaction with thedevice. Increasing the level of interactivity of a character andimproving the impression of natural motion displayed by a characterimprove the character's lifelike appearance, thereby enhancing andprolonging user interactions with the device. Enabling thecharacter-based interface to not only keep time, but also provideinformation related to other events, further enhances user interactionswith the device by conveying a more lifelike and interactivecharacter-based user interface.

Accordingly, provided herein are context-specific user interfaces thatinclude a character user interface object. A user may wish for suchcharacter-based user interface objects to adopt a more natural andlifelike appearance. Further, a user may wish for the character-baseduser interface object to act in a more dynamic manner, to interact withthe user, and/or to provide event-related information to a user.

Device 14000 may display a character user interface object such ascharacter user interface object 14604 on the display. Character userinterface object 14604 has representations of limbs 14606 and 14608. Asshown on user interface screen 14602, character user interface object14604 may indicate a time, for example 7:50, through the positions oflimbs 14606 and 14608.

A character user interface object may include any representation of acharacter, for example a human or anthropomorphized character. In someembodiments, a character may be a cartoon figure. In some embodiments, acharacter may be a realistic figure. In some embodiments, a charactermay be a human, animal, plant, other organism, or other object. In someembodiments a character may be a popularized character, such as acartoon character.

Character user interface object 14604 may indicate time by indicating anhour with a first limb (e.g., limb 14606) and by indicating a minutewith a second limb (e.g., limb 14608). In some embodiments, thecharacter user interface object may be a static image that is updatablefor different times. In some embodiments, the character user interfaceobject may be animated and may depict movement. For example, thecharacter user interface object may be animated to represent blinking ofeyes, shifting its weight, and/or changing an expression (e.g., facialexpression).

As described herein, a character user interface object may indicate atime through varying degrees of precision. As shown in FIG. 14B, a userinterface screen may include one or more numerical indications of timevalues, i.e., numbers that indicate hour, minute, or second values on aclock face. However, since users are accustomed to perceiving clockfaces, numerical indications of time values are optional, since therelative positioning of two objects resembling the hands of a clock mayindicate an approximate time even without such numerical indications.

Any of the user interface screens described herein may further includeone or more complications, such as indications of a date, a stopwatch, achronograph, an alarm, and the like.

In addition, limbs of a character user interface object may indicatetime to a user in various ways. For example, a limb (e.g., an arm or aleg) may indicate a time by its relative position on the display, or by“pointing” to a position on the display along a vector. A limb may alsoindicate a time by displaying an indicator of direction, such as arepresentation of a finger that indicates a position on the displaycorresponding to a time, either through its relative position or bypointing along a vector, as described above. A limb need not be precisein indicating a time.

Device 14000 may update the character user interface object to indicatea second time by reversing the roles of the first and second limbs,i.e., by indicating a second hour with the second limb and a secondminute with the first limb. For example, FIG. 14B shows user interfacescreen 14610 that device 14000 may display. User interface screen 14610includes character user interface object 14612. Character user interfaceobject 14612 may be the same character user interface object ascharacter user interface object 14604 but representing a different time.

As shown on user interface screen 14610, character user interface object14612 is indicating a time, for example 8:20, through the positions oflimbs 14614 and 14616. Comparing character user interface object 14604and 14612, both have a first limb (limb 14606 and limb 14614,respectively) and a second limb (limb 14608 and limb 14616,respectively). However, character user interface object 14604's firstlimb (limb 14606) is indicating an hour, whereas character userinterface object 14612's first limb (limb 14614) is indicating a minute.Similarly, character user interface object 14604's second limb (limb14608) is indicating a minute, whereas character user interface object14612's second limb (limb 14616) is indicating an hour.

In some embodiments, device 14000 may update the user interface objectto indicate a second time by extending the first limb and retracting thesecond limb. As a user may be accustomed to a standard clock face,wherein the hour hand is shorter than the minute hand, altering theextension and/or retraction of the limbs when reversing their roles maymake it easier for the user to keep track of the indicated times.

Allowing a character user interface object to indicate time using limbswith reversible roles increases the flexibility for displaying thecharacter user interface object by allowing the character to maintain anatural appearance at all times. Otherwise, if the roles of the limbswere fixed, the character might contort in an awkward way at certaintimes of day, for example, between 12:30 and 12:40. Enabling thecharacter to switch roles of the limbs affords more options forcharacter postures and positions that may represent a more naturalappearance, thereby enhancing the user's interactions with the device byportraying a more lifelike character user interface object.

Turning now to FIG. 14C, a user may wish to interact with a morenatural-looking character user interface object. If a character userinterface object indicates time with a limb that is always moving from afixed position or role, this diminishes the natural appearance of thecharacter because the range of motions and/or postures for the characteris restricted. This can lead awkward postures and/or monotonouscharacter appearance. A limb may indicate time via animationsrepresenting free movement from both endpoints of the limb, rather thana representation of rotation about an axis whereby one endpoint isalways fixed, making the character user interface object appear morenatural at different times of day.

It is understood that descriptions of mechanical motions (e.g., limbmotion) used herein encompass displaying representations or simulationsof mechanical motion.

FIG. 14C shows exemplary user interface screen 14702 that device 14000can display on its display. In some embodiments, device 14000 may be oneor more of devices 100 (FIG. 1), 300 (FIG. 3), and/or 500 (FIG. 5).

Device 14000 may display a character user interface object such ascharacter user interface object 14704 on the display. Character userinterface object 14704 has a representation of a limb 14706. As shown onuser interface screen 14702, character user interface object 14704 mayindicate a time, for example an hour such as 12, through the position oflimb 14706. In some embodiments, the character user interface object maybe a static image that is updatable for different times. In someembodiments, the character user interface object may be animated and maydepict movement.

Limb 14706 has a first endpoint 14708 at a first position that serves asa representation of an axis of rotation for limb 14706. That is, theposition of limb 14706 may be displayed or animated so as to representrotation about endpoint 14708 to display different times of day. Limb14706 also has a second endpoint 14710 at a second position thatindicates a time value. In some embodiments, a time value may be anhour, a minute, and/or a second.

Device 14000 may update character user interface object 14704 toindicate a second time value by moving first endpoint 14708 to a thirdposition, and moving second endpoint 14710 to a fourth position toindicate a second time value. Importantly, while first endpoint 14708serves as an axis of rotation for limb 14706, first endpoint 14708itself may also move to indicate time. Therefore, limb 14706 is able toadopt more natural postures because its positioning is afforded moreflexibility. This enhances the lifelike appearance of the character.

As an example, user interface screen 14720 shows character userinterface object 14722 with limb 14724 having first endpoint 14726 andsecond endpoint 14728. Character user interface object 14722 may be anupdated display of character user interface object 14704. Comparing userinterface screens 14702 and 14720, in particular limb 14706 and limb14724, the position of the first endpoint has been updated, as reflectedby the positions of first endpoints 14708 and 14726. First endpoint14726 is at the third position, and second endpoint 14728 is at a fourthposition to indicate the second time. As shown on user interface screens14702 and 14720, limb 14706 has been updated to limb 14724 by (i) movingthe position of first endpoint and (ii) rotating the limb at the axis ofrotation.

In some embodiments, a character user interface object may include arepresentation of a second limb, such as second limb 14712. Like thefirst limb, second limb 14712 also has a first endpoint 14714 that is anaxis of rotation for second limb 14712 and a second endpoint 14716. Theposition of second endpoint 14716 may indicate a third time value. Forexample, limb 14706 may indicate an hour value and limb 14712 mayindicate a minute value. Device 14000 may update character userinterface object 14704 to indicate a fourth time value by moving firstendpoint 14714 of the second limb 14712 to a third position, and bymoving second endpoint 14716 to a fourth position to indicate a secondtime value. This is depicted on user interface screen 14720, whichdepicts second limb 14730 with first endpoint 14732 at the thirdposition and second endpoint 14734 at the fourth position.

As described above, first and second limbs of a character user interfaceobject may each have two endpoints that may each change their position.In some embodiments, the first limb is connected to a torso at a firstshoulder, and the second limb is connected to the torso at a secondshoulder. In some embodiments, the torso connects the movements of eachlimb by each shoulder, such that a position of one shoulder may affect aposition of the other shoulder. This feature adds to the lifelike andnatural appearance of the character by coordinating or otherwiseinter-relating the movements of both limbs, as with a living body.

FIG. 14D shows exemplary user interface screen 14802 that device 14000can display on its display. In some embodiments, device 14000 may be oneor more of devices 100 (FIG. 1), 300 (FIG. 3), and/or 500 (FIG. 5).

Device 14000 may display a character user interface object such ascharacter user interface object 14804 on the display. Character userinterface object 14804 has a representation of a limb 14806. As shown onuser interface screen 14802, character user interface object 14804 mayindicate a time, for example an hour such as 12, through the position oflimb 14806.

Limb 14806 has a first segment 14808 with a first endpoint 14810 at oneend and a joint 14812 at the other. First endpoint 14810 has a firstposition. Limb 14806 also has a second segment 14814 with a secondendpoint 14816 at one end and joint 14812 at the other. Therefore, firstsegment 14808 and second segment 14814 connect at joint 14812, which isan axis of rotation for second segment 14814. Second endpoint 14816 atthe end of second segment 14814 (and hence, at one end of limb 14806)has a second position and indicates a first time value, for example anhour such as 12.

Device 14000 may update character user interface object 14804 toindicate a second time value by moving second endpoint 14814 along theaxis of rotation to a third position to indicate the second time.Described in anthropomorphic terms, limb 14806 has representations of anupper arm 14808 and a forearm 14814 joined at an elbow 14812. Forearm14814 may rotate at the elbow 14812 to indicate a different time. Addinga joint to a limb that indicates time is analogous to a hand of a clock,except that the arm is more natural looking than a clock hand because itincludes a joint. Further, the joint enhances the potential range ofmotions that may be depicted by the limb.

User interface screen 14820 illustrates this by displaying characteruser interface object 14822 with limb 14824. In some embodiments,character user interface object may be the same object as character userinterface object 14804 but in a different posture. Limb 14824 has afirst endpoint 14826, first segment 14828, and joint 14830. Joint 14830is connected to second segment 14832, which has second endpoint 14824.As demonstrated by comparing the features of character user interfaceobjects 14804 and 14822, second endpoint 14834 is at a differentposition than second endpoint 14816, thus indicating a different time.This change in position is accomplished by rotating the second segmentat the joint.

In some embodiments, moving the second endpoint may include depictingstatic images of the second endpoint at the first and third positions.In some embodiments, moving the second endpoint may include animatingthe character user interface object to translate the motion of thesecond endpoint on-screen.

In some embodiments, updating the character user interface object mayinclude moving the first endpoint. As shown by user interface screen14802 to user interface screen 14820, first endpoint 14810 may be movedto change the display of time, e.g., as shown by first endpoint 14826.Therefore, the character user interface object may have a limb that, inthe arm analogy above, may rotate the upper arm at the shoulder, maymove the shoulder itself, and may rotate the forearm at the elbow.

These features allow the character user interface object to assume awider range of natural and lifelike postures with which to indicatetime. If these features are animated on-screen, this allows thecharacter to simulate the motion of a moving figure such as a person.This greatly improves user interaction with and connection to the deviceby more accurately simulating a moving figure like a person. It allowsfor both subtle and dynamic movements, giving the character a widerrange of expressions that help simulate a personality of the character.Therefore, the character ceases to be a simple aggregation of twocharacter-like clock hands that can only tell time and becomes more likean actual character that can express a personality, thereby enhancingthe user's experiences with the device.

In some embodiments, the character user interface object (e.g.,character user interface object 14804 and/or 14822) also includes arepresentation of a second limb, such as second limb 14818 as shown onuser interface screen 14802 or second limb 14836 as shown on userinterface screen 14820. As described above in reference to the firstlimb, a second limb may include a first segment connecting a firstendpoint of the second limb to a joint and a second segment connecting asecond segment to the joint. The first endpoint of the second limb maybe at a first position, and the second endpoint of the second segmentmay be at a second position. The joint may serve as an axis of rotationfor the second segment, which may indicate a third time value. Device14000 may update the character user interface object by moving thesecond endpoint of the second limb along the axis of rotation at thejoint to indicate a fourth time value.

In some embodiments, the first limb indicates an hour and the secondlimb indicates a minute. In some embodiments, the first limb indicates aminute and the second limb indicates an hour. The first limb and thesecond limb may be distinguished, for example, by length, as withtraditional clock hands. The first limb and the second limb may bedistinguished, for example, by the distance between the first and secondendpoints. For example, one limb may be bent or the shoulder may bepositioned such that, even though it may not be shorter than anotherlimb, it appears shorter or otherwise distinct from another limb. Thefirst limb and the second limb may be distinguished, for example, by thedistance between the second endpoint and another object on the display,such as a numerical indication of time.

In some embodiments, updating the character user interface object toindicate the second time may include animating the character userinterface object by translating the first endpoint on-screen. Forexample, the character may appear to move one or both shoulders. In someembodiments, the movement or position of one shoulder may affect themovement or position of another shoulder, simulating the connectedmotion of an actual figure such as a human.

In some embodiments, updating the character user interface object toindicate the second time may include animating the character userinterface object by rotating the second segment at the joint on-screen.For example, the second segment may rotate at the joint like a forearm.

In some embodiments, the character user interface object may alsotranslate on-screen, for example towards a center of the display.

FIG. 14E shows exemplary user interface screen 14902 that device 14000can display on its display. In some embodiments, device 14000 may be oneor more of devices 100 (FIG. 1), 300 (FIG. 3), and/or 500 (FIG. 5).Device 14000 may display a character user interface object such ascharacter user interface object 14904 on the display. User interfacescreen 14902 shows the translation of the character by sequentialdisplays of character user interface object 14904 at two differentlocations, first at location 14906 and then at location 14908. Characteruser interface object 14904 is closer to the center of the display atlocation 14908, thus simulating motion in the right-to-left direction asshown in FIG. 14E. Motion such as this may be used, for example, whenthe user initiates an interaction with the device or looks at thedevice, which prompts the character to move to the center of the displayand indicate a time.

In some embodiments, translating the character user interface object mayinclude animating the character user interface object to representwalking, for example to the center of the display. Character userinterface object 14904 illustrates this by depicting a character withlegs and a torso. The different positions and postures represented bythe legs and the torso of character user interface object 14904 atlocations 14906 and 14908 represent walking. For example, in response tothe user interacting with the device, the character may be animated towalk naturally onto the screen and then assume a position correspondingto the current time. The user interaction may include activating thescreen, raising the device into a viewing position, pressing a button onthe device that corresponds to activating a watch face, etc.

FIG. 14F shows exemplary user interface screen 15002 that device 14000can display on its display. In some embodiments, device 14000 may be oneor more of devices 100 (FIG. 1), 300 (FIG. 3), and/or 500 (FIG. 5).Device 14000 may display a character user interface object such ascharacter user interface object 15004 on the display. Device 14000 maychange a visual aspect of the displayed user interface screen tohighlight the character user interface object. FIG. 14F illustrates anexemplary embodiment of this concept. User interface screen 15002includes a spotlight 15006 that highlights character user interfaceobject 15004.

In some embodiments, changing a visual aspect of the display couldinclude one or more of changing the color and/or brightness of the userinterface screen around the character user interface object, displayinga user interface object such as a spotlight, and so forth.

In some embodiments, device 14000 may animate the character userinterface object to represent a response by the character user interfaceobject to the changing of the visual aspect. As shown in the exemplaryembodiment of FIG. 14F, character user interface object 15004 may beanimated to simulate looking at spotlight 15006.

FIG. 14G shows exemplary user interface screen 15102 that device 14000can display on its display. In some embodiments, device 14000 may be oneor more of devices 100 (FIG. 1), 300 (FIG. 3), and/or 500 (FIG. 5).Device 14000 may display a character user interface object such ascharacter user interface object 15104 on the display. Character userinterface object 15104 may include a representation of a foot 15106. Insome embodiments, character user interface object 15104 includes twolimbs that indicate time values and two legs, at least one of which mayinclude a foot.

In some embodiments, device 14000 may animate the foot to indicatepassage of time. As shown on user interface screens 15102 and 15110,character user interface objects 15104 and 15112 include a foot (15106and 15114, respectively). The different positions of feet 15106 and15114 (different with respect to the position on the display and/ortheir posture within the character user interface object) depict thisanimation. For example, the character may be animated to simulate amotion of the foot, such as tapping. This may have a regular orirregular timing. In some embodiments, the foot is animated to move at aregular interval, such as once every second. When coupled with twolimbs, this allows the character user interface object to depict, forexample, hour, minute, and second time values.

In some embodiments, the first time and the second time depicted by thecharacter user interface object are the same. In other words, thecharacter user interface object may move by shifting a limb or anyendpoint of a limb without depicting a different time. This allows thecharacter to shift posture without changing the indicated time.

In some embodiments, the display may include one or more numericalindications of time. For example, the display may include arepresentation of a circular clock face with a character user interfaceobject in the center encircled by numerical indicators, as with a clock.

The features described above allow a character user interface object toappear more natural and lifelike by adopting a wider range of naturalmotions while indicating a time. A user may wish to view representationsof other events by the character user interface object. Allowing thecharacter user interface object to react to external stimuli or internalsystem events portrays a more interactive character, thus depicting acloser representation of a personality. The enhanced interactivity ofthe character further improves the user's interactions with the deviceby providing additional notification that an event has occurred, theoccurrence of which may not have been as apparent otherwise. A characteruser interface object may serve to supply notifications, reminders,and/or other information a user may wish to access from a personalelectronic device, but the use of a character provides an interactivepersonality that the device may use to supply these items. Further,making the character responsive to internal system events (e.g.,calendar events and the like) means the character is not strictlylimited to responding to external user input. Put another way, thecharacter appears to have a more lifelike personality because itresponds to events not directly prompted by the immediate actions of theuser.

FIG. 14H shows exemplary user interface screen 15202 that device 14000can display on its display. In some embodiments, device 14000 may be oneor more of devices 100 (FIG. 1), 300 (FIG. 3), and/or 500 (FIG. 5).Device 14000 may display a character user interface object such ascharacter user interface object 15204 on the display. Character userinterface object 15204 indicates time as described above.

Device 14000 may receive first data indicative of an event. Device 14000may determine whether the event meets a condition. In accordance withthe determination that the event meets the condition, device 14000 mayupdate character user interface object 15204 by changing a visual aspectof the character user interface object.

In some embodiments, after updating the displayed character userinterface object, the character user interface object still indicatestime. For example, the appearance or posture of the character may bealtered, but the character still indicates time.

In some embodiments, after updating the displayed character userinterface object, the character user interface object no longer onlyindicates time. For example, the character may adopt a posture, assume afacial expression, or use its limbs for a function other than indicatingtime, such as conveying a meaning related to the event and/or thecondition.

In some embodiments, the first data indicates a calendar event. Device14000 may receive data indicating a calendar event, for example, byobtaining data representing the event from a calendar application ondevice 14000. In this example, the condition may correspond to aduration of the calendar event. Determining whether the event meets thecondition may include determining whether a current time is within theduration of the calendar event. For example, device 14000 may obtain acurrent time and determine whether the current time is within a durationof the calendar event (e.g., during the calendar event, or substantiallycontemporaneous with the calendar event but slightly preceding orslightly delayed after it).

An exemplary embodiment is shown on user interface screen 15202. In someembodiments, the calendar event is a birthday. In some embodiments, thebirthday is a user's birthday. In some embodiments, updating thedisplayed character user interface object may include animating thecharacter user interface object to display a birthday greeting.Character user interface object 15204 is animated to display festive hat15206 and birthday banner 15208. This animation serves to notify theuser of a birthday while making the character more interactive.Importantly, the character may change a visual aspect, such as bydisplaying a birthday greeting, without immediate input by the user,thus giving the impression that the character is able to act moreautonomously, as with a personality. In some embodiments, themodification of the character is an indication of some important eventrelated to one of the user's contacts, such as their birthday,anniversary, etc.

An exemplary embodiment is shown on user interface screen 15210. In someembodiments, the calendar event is a holiday. In some embodiments,updating the displayed character user interface object may includechanging a visual aspect of the character user interface object toreflect the holiday. In this example, character user interface object15212 depicts this through Santa Claus hat 15214. This animation servesto notify the user of the holiday while making the character moreinteractive and decreasing the monotony of character appearance. Otherexamples of holidays besides Christmas may include New Year's Eve or NewYear's Day, Thanksgiving, Hanukkah, the 4^(th) of July, St. Patrick'sDay, Valentine's Day, and the like.

In some embodiments, device 14000 may receive data indicating a userpreference, such as a user's favorite sports team. In accordance withreceiving the data, device 14000 may update character user interfaceobject 15204 by changing a visual aspect of the character user interfaceobject to reflect the sports team. For example, the appearance of thecharacter user interface object may be updated to portray the characteruser interface object wearing a uniform or other paraphernaliarepresenting the sports team (e.g., a hat, jersey, uniform, or otherrepresentation include a logo, icon, or text representing the sportsteam). The display may also be updated to include with the characteruser interface object a second user interface object representing asports object associated with the team's sport (e.g., a baseball batand/or baseball, football, basketball, soccer ball, hockey stick and/orhockey puck, checkered flag, and so forth). The character may be updatedin accordance with a determination that the team is playing that day orat that time, or in accordance with a determination that the user isgoing to attend an event featuring the team. The determination that theuser is going to attend an event featuring the team may be made throughan analysis of the user's calendar events or through a determinationthat an electronic ticket for an event is present on the electronicdevice or a paired electronic device. It is understood that a user'sfavorite sports team is merely an exemplary user preference, and otheruser preferences such as a representation of a flag or country are alsocontemplated.

FIG. 14I shows exemplary user interface screen 15302 that device 14000can display on its display. In some embodiments, device 14000 may be oneor more of devices 100 (FIG. 1), 300 (FIG. 3), and/or 500 (FIG. 5).Device 14000 may display a character user interface object such ascharacter user interface object 15304 on the display. Character userinterface object 15304 indicates time as described above.

Device 14000 may receive data indicating a notification. A notificationmay include, for example, an email, text message, reminder, virtualassistant request, or other such notification. Device 14000 may furtherdisplay the notification, or an affordance or user interface objectrepresenting receipt and/or a content of the notification, on userinterface screen 15302, as depicted by notification 15306. Device 14000may animate character user interface object 15304 to react tonotification 15306. For example, as shown on user interface screen15302, character user interface screen 15304 may appear to look atnotification 15306. This may include, for example, a change in posturesuch that the character faces the notification, or a change in theappearance of the character, such as a face, to indicate looking in thedirection of the notification. Again, by providing this change inposture or change in the character's focus, the user may be notified ofan incoming alert or event that may otherwise have been less apparent.

FIG. 14J shows exemplary user interface screen 15402 that device 14000can display on its display. In some embodiments, device 14000 may be oneor more of devices 100 (FIG. 1), 300 (FIG. 3), and/or 500 (FIG. 5).Device 14000 may display a character user interface object such ascharacter user interface object 15404 on the display. Character userinterface object 15404 indicates time as described above.

Device 14000 may receive first data indicating a time of day. A time ofday could include a current time. Device 14000 may determine that thetime of day meets a condition, such as by determining whether the timeof day is within the nighttime portion of the day. Device 14000 maychange a visual aspect of character user interface object 15404 torepresent nighttime. As shown in user interface screen 15402, characteruser interface object 15404 represents nighttime by depicting a yawn andholding candle 15406. In some embodiments, character user interfaceobject 15404 may be altered to depict wearing clothing associated withnighttime, such as pajamas. In some embodiments, the character interfaceobject is modified to yawn or wear pajamas in accordance with adetermination that the user should go to sleep. The determination may bebased on, for example, any of a preset time, recognition of a pattern ofthe user's sleep, indication of an early event on the next day'scalendar, recognition that the user has been active for longer than apredetermined time, etc.

FIG. 14K shows exemplary user interface screen 15502 that device 14000can display on its display. In some embodiments, device 14000 may be oneor more of devices 100 (FIG. 1), 300 (FIG. 3), and/or 500 (FIG. 5).Device 14000 may display a character user interface object such ascharacter user interface object 15504 on the display. Character userinterface object 15504 indicates time as described above.

Device 14000 may receive data indicating a current time. Device 14000may determine whether the current time corresponds to an hour on thehour (for example, 1:00, 2:00, and so forth). Device 14000 may determinewhether the current time is an hour on the hour and if so, animate thecharacter user interface object to announce the hour on the hour for oneor more hours. As shown in user interface screen 15502, character userinterface object 15504 announces the current hour by depicting musicalnote 15506. In some embodiments, the announcement of the hour couldinclude a visual depiction of an announcement, such as by displaying auser interface object. In some embodiments, the announcement of an hourcould include a sound such as a whistle, chime, one or more spokenwords, or a bell toll.

FIG. 14L shows exemplary user interface screen 15602 that device 14000can display on its display. In some embodiments, device 14000 may be oneor more of devices 100 (FIG. 1), 300 (FIG. 3), and/or 500 (FIG. 5).Device 14000 may display a character user interface object such ascharacter user interface object 15604 on the display. Character userinterface object 15604 indicates time as described above.

Device 14000 may receive data indicating current or forecasted weather.To receive data indicating current or forecasted weather, device 14000may retrieve weather information from an external server. In someembodiments, device 14000 may retrieve weather information from aweather service, such as The Weather Channel, Accuweather, The NationalWeather Service, Yahoo! ™ Weather, Weather Underground, and the like.

Device 14000 may determine whether the current or forecasted weathercorresponds to one or more designated weather conditions. Designatedweather conditions may be system-designated and may include favorableweather conditions such as sunshine or inclement weather conditions suchas rain, thunderstorms, wind, snow, and so forth. If device 14000determines that the current or forecasted weather corresponds to one ormore designated weather conditions, device 14000 may update thecharacter user interface object to reflect the current or forecastedweather. For example, as shown in FIG. 14L, user interface screen 15602includes character user interface object 15604 with umbrella 15606, aswell as raindrops 15608. In some embodiments, device 14000 may display auser interface object to reflect the designated weather condition. Insome embodiments, the character user interface object may be animated toreact to the user interface object reflective of a designated weathercondition. As another example, user interface screen 15610 displayscharacter user interface object 15612 with sunglasses 15614 andsurfboard 15616, as well as sun 15618.

FIG. 14M shows exemplary user interface screen 15702 that device 14000can display on its display. In some embodiments, device 14000 may be oneor more of devices 100 (FIG. 1), 300 (FIG. 3), and/or 500 (FIG. 5).Device 14000 may display a character user interface object such ascharacter user interface object 15704 on the display. Character userinterface object 15704 indicates time as described above.

Device 14000 may receive data indicating a second electronic device.Device 14000 may determine whether the data corresponds to a thresholdproximity of the second electronic device to device 14000. If so, device14000 may update character user interface object 15704 by animating thecharacter user interface object to react to the second electronicdevice. As shown in user interface screen 15702, character userinterface object 15704 may depict thumbs up 15706 or smile 15708. Insome embodiments, the posture of the character user interface object maybe updated to reflect the proximity and/or direction of the seconddevice. For example, the character user interface object may react inthe direction of the device or be reflected on the display. In someembodiments, data indicating a second electronic device may be providedthrough a server, which may provide the location of the user's contactsthat have agreed to provide their location data, such as Find MyFriends. Data indicating a second electronic device may also be providedthrough a local network, for example, a recognition that one of theuser's contacts has joined the same WiFi network. Data indicating asecond electronic device may also be provided by the second electronicdevice itself, such as the second electronic device announcing itselfthrough Bluetooth, Near Field Communication, etc.

In some embodiments, a device (such as device 14000) displaying acharacter user interface object indicating time may receive dataindicating user activity. For example, the device may include a useractivity monitor (such as a workout monitor), an accelerometer, agyroscope, a motion sensor, and/or a combination thereof. The device maydetermine whether the data indicating user activity is received outsideof a threshold interval after a previous user activity. For example, thedevice may determine whether a threshold period of time has elapsedsince the last data indicating user activity (e.g., the last userworkout). If the device determines that the data indicating useractivity is received outside of the threshold interval after a previoususer activity, the device may animate the character user interfaceobject to reflect inactivity. For example, the character may change anexpression and/or posture to represent boredom, a sedentary or recumbentposture, a sullen or apathetic appearance, and so forth.

FIG. 14N shows exemplary user interface screen 15802 that device 14000can display on its display. In some embodiments, device 14000 may be oneor more of devices 100 (FIG. 1), 300 (FIG. 3), and/or 500 (FIG. 5).Device 14000 may display a character user interface object such ascharacter user interface object 15804 on the display. Character userinterface object 15804 indicates time as described above.

Device 14000 may receive data indicating user activity. For example, thedevice may include a user activity monitor (such as a workout monitor),an accelerometer, a gyroscope, a motion sensor, and/or a combinationthereof. Device 14000 may determine whether the user activity is currentuser activity, and, if so, animate character user interface object 15804to represent exercise. For example, user interface screen 15802 includescharacter user interface object 15804 and barbell 15806. In someembodiments, device 14000 may animate the character user interfaceobject to depict an activity related to exercise, such as motion,running, weight lifting, swimming, bicycling, pushups, and/or sweat,heavy breathing, or any other signs of physical exertion. In someembodiments, the activity monitor may include options for the user toindicate which activity they are going to begin. In these cases thecharacter appearance may be changed to reflect the selected activityoption.

FIG. 14O shows exemplary user interface screen 15902 that device 14000can display on its display. In some embodiments, device 14000 may be oneor more of devices 100 (FIG. 1), 300 (FIG. 3), and/or 500 (FIG. 5).Device 14000 may display a character user interface object such ascharacter user interface object 15904 on the display. Character userinterface object 15904 indicates time as described above.

Device 14000 may receive data indicating user movement of the device,for example by using an accelerometer, directional sensor (e.g.,compass), gyroscope, motion sensor, and/or a combination thereof, and soforth. Device 14000 may determine whether the data indicating usermovement is received outside of a threshold interval after a previoususer movement. For example, device 14000 may determine whether athreshold period of time has elapsed since the last data indicating usermovement (e.g., picking up the device, a motion indicative of a userwrist movement, and so forth). If device 14000 determines that the dataindicating user movement is received outside of the threshold intervalafter a previous user movement, device 14000 may animate the characteruser interface object to indicate fatigue. For example, user interfaceobject 15904 includes limbs 15906 and 15908. Device 14000 may animatecharacter user interface object 15904 to droop one or more of limbs15906 and 15908. In some embodiments, device 14000 may animate characteruser interface object 15904 to shift position, portray physical effort,and the like.

FIG. 14P shows exemplary user interface screen 16002 that device 14000can display on its display. In some embodiments, device 14000 may be oneor more of devices 100 (FIG. 1), 300 (FIG. 3), and/or 500 (FIG. 5).Device 14000 may display a character user interface object such ascharacter user interface object 16004 on the display. Character userinterface object 16004 indicates time as described above.

Device 14000 may receive data indicating a user contact on thetouch-sensitive surface (e.g., a touchscreen). Device 14000 maydetermine whether the user contact corresponds to a user contact oncharacter user interface object 16004. In some embodiments, the usercontact may be on a touchscreen at the position of the character userinterface object. In some embodiments, the user may input information tomanipulate a cursor or other indicator to contact the displayedcharacter user interface object. For example, as shown on user interfacescreen 16002, a user may contact character user interface object 16004with touch 16006.

If device 14000 determines that the user contact corresponds to a usercontact on character user interface object 16004, device 14000 mayanimate character user interface object 16004 to react to the contact.In some embodiments, the reaction may be a specific to the location ofthe contact on the character user interface object. In some embodiments,the reaction may be a general reaction. In some embodiments, thereaction may include, for example, reacting as to tickling, hugging, orother forms of friendly contact. In some embodiments, character userinterface object 16004 may display a second animation distinct from thefirst animation in response to a second user contact.

FIG. 14Q shows exemplary user interface screens 16102 and 16202 thatdevice 14000 can display on its display. In some embodiments, device14000 may be one or more of devices 100 (FIG. 1), 300 (FIG. 3), and/or500 (FIG. 5). Device 14000 may display character user interface object16104 on the display. Character user interface object 16104 indicatestime as described above. As shown in FIG. 14Q, in some embodiments,character user interface object 16104 may depict a facial expression,such as a yawn. In some embodiments, character user interface object16204 may depict speech, such as by presenting text in a displayed userinterface object or affordance representing speech balloon 16206 or athought balloon. Speech may be depicted to visually present anannouncement made by a character user interface object, such as anannouncement of the hour as described above with reference to characteruser interface object 15504 in FIG. 14K.

FIG. 14R shows exemplary user interface screens 16302 and 16402 thatdevice 14000 can display on its display. In some embodiments, device14000 may be one or more of devices 100 (FIG. 1), 300 (FIG. 3), and/or500 (FIG. 5). Device 14000 may display character user interface object16304. Character user interface object 16304 indicates time as describedabove. As shown in FIG. 14R, in some embodiments, character userinterface object 16304 may depict boredom or fatigue, as describedabove. In some embodiments, the character user interface object maydepict attire. For example, character user interface object 16404 maydepict a sports team or a sports object (e.g., baseball 16406 and bat16408), such as those representing the user's favorite sports team, asdescribed above.

FIG. 14S shows exemplary user interface screen 16502 that device 14000can display on its display. In some embodiments, device 14000 may be oneor more of devices 100 (FIG. 1), 300 (FIG. 3), and/or 500 (FIG. 5).Device 14000 may display character user interface object 16504.Character user interface object 16504 indicates time as described above.As shown in FIG. 14S, in some embodiments, character user interfaceobject 16504 may depict a facial expression, such as blinking, closing,or winking one or more the eyes. The character interface object maychange facial expression at predetermined or random intervals to providean indication to the user that the interface is still active.

FIG. 14T shows exemplary user interface screen 16602 that device 14000can display on its display. In some embodiments, device 14000 may be oneor more of devices 100 (FIG. 1), 300 (FIG. 3), and/or 500 (FIG. 5).Device 14000 may display a character user interface object on thedisplay. The displayed character user interface object indicates time asdescribed above. As shown in FIG. 14T, in some embodiments, thecharacter user interface object includes one or more second endpoints,such as a second endpoint of a limb and a second endpoint of a secondlimb, as described above. In some embodiments, the second endpoint 16604of a first limb may indicate an hour and be positioned along thecircumference of a first circle 16606. The second endpoint 16608 of asecond limb may indicate a minute and be positioned along thecircumference of a second circle 16610 that encircles the first circle16606 and has a larger circumference than the first circle 16606. Inthis way, the user may distinguish which limb indicates an hour andwhich limb indicates a minute by the relative closeness to an edge ofthe display or to one or more displayed numerical indications of time.

In some embodiments, a device (such as device 14000) may detect a userinput and, in response to detecting the user input, display a characteruser interface object. For example, the display of the device may showanother display or be dark, then display the user interface object onthe screen in response to the user input. In some embodiments, the userinput may be a movement of the device (e.g., picking up the device, amotion indicative of a user wrist movement, and so forth). In someembodiments, the user input may be a touch on the touch-sensitivesurface (e.g., a touchscreen).

Turning now to FIG. 14U, users rely on personal electronic devices tokeep time throughout the day. It is becoming increasingly desirable topresent the user with interactive user interfaces that promote userinteraction with a personal electronic device. Indicating the timethrough a cardinal-numbers-based user interface may enhance a user'sinteraction with the device. Increasing the level of simplicity of theinterface screen, while still providing adequate cardinal numbers forsimple and intuitive timekeeping, may increase the space available onsmall devices for additional information to be displayed, therebyenhancing and prolonging user interactions with the device.

Accordingly, provided herein are context-specific user interfaces thatinclude a clock face featuring four cardinal numbers. A user may wishfor such cardinal-numbers-based user interface to be easily readable andto leave adequate room (especially at the corners of a square screen)for additional information.

FIG. 14U shows exemplary user interface screen 16702 that device 14000can display on its display. In some embodiments, device 14000 may be oneor more of devices 100 (FIG. 1), 300 (FIG. 3), and/or 500 (FIG. 5).

Device 14000 may display interface 16702, including a clock facecomprising one or more cardinal numbers. The clock face may be arepresentation of an analog clock featuring an hour hand, a minute hand,and a second hand. The cardinal numbers may each correspond to one ofthe 12 numbers that traditionally appear on a clock face, and they mayappear in a position on the display corresponding to the respectivenumber's usual position on a clock face. For example, the number “12”may appear at the top center of the display, the number “3” at thecenter right, the number “6” at the bottom center, and the number “9” atthe center left. In some embodiments, fewer than four cardinal numbersmay be used, such as only three or only two. In some embodiments,numbers other than “12,” “3,” “6,” and “9” may be used; for example,interface 16702 could display a clock face featuring only the numbers“10, “2,” and “6.”

In some embodiments, the cardinal numbers displayed on interface 16702may be displayed at a large enough size such that all 12 numbers of atraditional clock face could not be simultaneously displayed on adisplay of device 14000 at the same size. The smaller number of cardinalnumbers displayed may thus be easier to read due to their larger size.In some embodiments, the number of cardinal numbers displayed ismaintained at less than 12, even though sufficient space is available todisplay additional numbers, in order to maintain simplicity.

In some embodiments, a user is able to modify font settings and colorsettings of the cardinal-numbers-based interface. In some embodiments,different fonts may be used to render one or more of the displayedcardinal numbers. The same font may be used for all of the cardinalnumbers, or a different font may be used for one or more of the numbers.In some embodiments, the font used is a system font that is a defaultfont for an operating system of device 14000. In some embodiments, otherfonts are available that reflect modifications or stylizations of thedefault system font. For example, fonts may be used that reflect ashadowed stylization of the system font, a rounded stylization of thesystem font, a striped stylization of the system font, a stencilstylization of the system font, an embossed stylization of the systemfont, a bold stylization of the system font, an italic stylization ofthe system font, etc. Stylizations of the system font may be used inplace of or in addition to fonts that are unrelated to the system font.Using stylizations of the system font may create a consistent look andfeel to the interface of the device while still allowing the user tocustomize the font.

In some embodiments different colors may be selected by a user to applyto all of the cardinal numbers or to one of the individual cardinalnumbers. In some embodiments, a user may select a color theme thatapplies to one or more of the cardinal numbers, or to all of thecardinal numbers; a theme may be a curated selection of colors that arepredetermined to correspond to one another. In some embodiments, a usermay select an option to apply a gradient color scheme to one or more ofthe cardinal numbers. In some embodiments, a user may select an optionto apply a color setting to one or more of the cardinal numbers suchthat the color or colors of the one or more cardinal numbers change overtime, either according to a predetermined schedule or in accordance withcontextual factors.

In some embodiments, a user may set the font settings or color settingsof the device from an edit interface. For example, a user may apply ahard-press to the clock face of interface 16702 to activate an editstate. In the edit interface, a user may tap the clock face or aspecific cardinal number to select one or more of the cardinal numbers.The selected one or more cardinal numbers may be highlighted in anysuitable manner, including by being displayed in a larger size, toindicate that the one or more cardinal numbers are selected for editing.While the one or more cardinal numbers are selected for editing, theuser may rotate a rotatable input mechanism of device 14000 in order tochange the font or color setting by scrolling through settings. Thesetting may be arranged in an ordered progression such that the user mayscroll through the available choices. In some embodiments, the orderedprogression may loop around from one end to the other, such that whenthe user reaches the final setting in the ordered progression, he mayproceed in the same direction to the first setting in the orderedprogression.

In some embodiments, in the edit interface, paging dots may appear atthe top of the interface to indicate to the user how many differentpages are available in the edit interface. For example, an editinterface may have two pages, a first for editing color and a second forediting font. As described above, a user may select one or more of thecardinal numbers for editing in on one of the pages, and may use therotatable input mechanism to change the setting. A user may then performa horizontal swipe input detected by device 14000 in order to page tothe adjacent page. For example, if the leftmost page is a page forediting color, then a user may swipe to the left in order to page to theright and access a page for editing font. At the font editing page, theuser may edit font settings in a similar manner as described above. Insome embodiments, a selection of one or more of the cardinal numbers forediting is maintained when a user pages between pages in the editinterface, while in other embodiments selections are cleared when a userpages.

In some embodiments, the edit interface may include additional pages forediting additional settings, or may enable editing one or more settingsof the interface (such as an information density setting) in response torotation of the rotatable input mechanism without having any of thecardinal numbers selected for editing.

In some embodiments, interface 16702 may display, in addition to theclock face, one or more other user interface objects, such ascomplications, that present information to the user. In someembodiments, the complications displayed may be customizable by the userin accordance with the methods described above. In some embodiments,complications may be displayed in predefined locations in interface16702, such as at the corners. There may be sufficient room for clearand unobstructed display of complications in the corners of interface16702 because the cardinal numbers may not occupy that space. In someembodiments, interface 16702 may feature no complications or other userinterface objects, and may feature only the cardinal-numbers clock face.

2. Editing Context-Specific User Interfaces

The context-specific user interfaces described and illustrated hereinprovide numerous elements and features that a user may customize,depending upon a particular context. As described, these customizableelements enhance the user interfaces, making them more personal andinteractive to the user.

At the same time, a user also wants a device that is easy and intuitiveto use. Providing a multitude of features only serves to frustrate theuser if the user interface does not provide comprehensible ways to editthese features. Described below are user interfaces for editingcontext-specific user interfaces that provide easy and intuitive methodsthat facilitate user customization.

Importantly, it is to be appreciated that, while particular embodimentssuch as clock faces may be described with respect to particular editingfeatures, these editing features may also apply to one or more of theother user interfaces described herein. For example, a method forcustomizing a color of a clock face may be used to change the color of aseconds hand, change an animated object (e.g., a butterfly), or change aclock face background (e.g., a photo or image of a scene). Similarly,methods for customizing complications may be used to add and/or editvarious complications on any clock face, regardless of whether anembodiment of that clock face bearing a particular complication wasdescribed herein. A skilled artisan will recognize that the methodsdescribed below provide user interface functionalities that may beapplied to elements and aspects of various context-specific userinterfaces in numerous combinations, such that each possible combinationwould be impossible to elaborate individually.

It is to be further appreciated that references to a “clock face” withrespect to clock face editing and/or selection as described herein arenot in any way limited to a traditional notion of a “clock face,” e.g.,a circular display with hour indications and one or more hands toindicate time, or a representation of a digital clock. Anycontext-specific user interface with an indication of time describedherein may properly be termed a clock face.

Attention is now directed to FIG. 15. FIG. 15 shows exemplarycontext-specific user interfaces that may be operated on device 1500.Device 1500 may be device 100, 300, or 500 in some embodiments. Theelectronic device has a touch-sensitive display (e.g., touchscreen 504)configured to detect the intensity of contacts. Exemplary components fordetecting the intensity of contacts, as well as techniques for theirdetection, have been referenced and described in greater detail above.

Device 1500 displays user interface screen 1502, which includes clockface 1504. Clock face 1504 also includes complication 1506 that displaysa set of information from a weather application (e.g., current weatherconditions). In this example, the user wishes to change multiple aspectsof clock face 1504. Specifically, the user decides to change the hourindications on clock face 1504 and complication 1506.

The user contacts the touch-sensitive display of device 1500 with touch1508. Touch 1508 has a characteristic intensity above an intensitythreshold, which prompts device 1500 to enter a clock face edit mode,shown on screen 1510. Clock face edit mode allows the user to edit oneor more aspects of a clock face. Device 1500 indicates that the user hasentered clock face edit mode by visually distinguishing the clock face.In this example, screen 1510 shows a smaller version of the display ofscreen 1502 (e.g., 1512), which includes reduced size clock face 1514based on clock face 1504. Reduced size complication 1516, which is basedon complication 1506, is also displayed. This display indicates to theuser that the user is in clock face edit mode while giving the user anindication of what the edited clock face will look like on the display.In some embodiments, a user may be able to select a different clock faceby swiping displayed screen 1510, as described in greater detail belowin reference to FIGS. 16A-C.

Screen 1510 also displays paging affordance 1518. Paging affordances mayindicate where the user is within a sequence of options, as well as howmany options are available in the sequence. In clock face edit mode,paging affordances may indicate which editable aspect of the clock facea user is editing, where this aspect falls within a sequence of editableaspects, and the total number of editable aspects in the sequence (ifclock face selection is available on this screen, paging affordance 1518may depict the currently selected clock face within a sequence ofselectable clock faces and/or clock face options, as described below). Apaging affordance may be advantageous in clock face edit mode to helpthe user navigate the interface and explore all of the editable optionsavailable within each type of clock face.

The user selects the displayed clock face for editing by contacting 1512through touch 1520. In response to detecting touch 1520, device 1500visually indicates an element of the clock face for editing. As shown onscreen 1530, the hour indications have been selected for editing, asindicated by outline 1534 around the position of the hour indications.The other elements of the clock face are still retained, as shown byhour hand and minute hand 1532 and complication 1536.

In this example, three aspects of the clock face are available for userediting. This is depicted by paging affordance 1538. The first editableaspect is the hour indications (e.g., their number and/or appearance).This is relayed to the user by paging affordance 1538. By viewingoutline 1534 in combination with paging affordance 1538, the userrecognizes that the hour indications are the first of three editableaspects of this clock face.

Device 1500 also has rotatable input mechanism 1540. The user may moverotatable input mechanism 1540 to cycle through different options forediting different aspects of the clock face. On screen 1530, the usermay select different options for the hour indications (which arecurrently editable, as depicted by outline 1534) through movement 1542.Advantageously, using a rotatable input mechanism to cycle throughediting options (rather than using, e.g., a touch interaction) frees uptouch interactions with the screen to instead provide otherfunctionalities, thus expanding the interactability of the device. Usinga rotatable input mechanism is also helpful in cases where smallerelements of the display are being edited, as finer-scale touch gesturesmay be difficult on a reduced-size display for users with large fingers.

Also displayed on screen 1530 is positional indicator 1544, shown as acolumn of 9 lines. Positional indicator 1544 is an indicator of acurrent position along a series of positions. This is may be used, forexample, in combination with rotatable input mechanism 1540. On screen1530, positional indicator 1544 indicates to the user the position ofthe currently selected option (e.g., by line 1546) within a series ofall selectable options.

Upon detecting movement 1542, device 1500 displays screen 1550. Inresponse to detecting movement 1542, device 1500 edits the hourindications, in this case by increasing the number of indications andadding numerals. This is shown by indications 1552, still highlighted byoutline 1534. The other elements of the clock face, hour hand and minutehand 1532 and complication 1536, remain the same. Positional indicator1544 has been updated to indicate the position of this hour indicationoption, highlighted by line 1554, within a series of positions of hourindication options.

As indicated by paging affordance 1538, the hour indications are thefirst editable aspect of this clock face within a sequence of editableaspects. The user may select a second editable aspect by swiping thetouch-sensitive display (e.g., swipe 1556). In response to detecting theswipe, device 1500 displays screen 1560. Screen 1560 includes clock face1562, which now has 12 hour indications, including 4 numericalindications, as depicted by hour indications 1552. Note that these hourindications are the hour indications that were selected by the user onthe previous screen (see indications 1552). Paging affordance 1538 hasnow been updated to indicate that editing complications is the secondeditable aspect within the sequence of editable aspects in this clockface.

On screen 1560, complication 1536 is currently editable, as indicated tothe user by outline 1564. Currently, complication 1536 is displayingcurrent weather conditions using information from a weather application.This option is option 3 in a series of options, as indicated by updatedpositional indicator 1544 and line 1566. Positional indicator 1544 letsthe user know that the currently selected feature (i.e., complication1536) is editable by the rotatable input mechanism.

While screen 1560 depicts a single complication, it should be understoodthat multiple complications may be displayed. When multiplecomplications are displayed, a user may select a particular complicationfor editing by contacting the corresponding position of thecomplication. Outline 1564 then transitions from the previously selectedcomplication or element to the currently selected complication orelement and rotatable input mechanism may then be used to edit thecomplication or element at the selected location. This concept isdescribed in greater detail below in reference to FIG. 18C.

It is to be noted that positional indicator 1544 is displayed on screens1530, 1550, and 1560, even though the available options depicted by theindicators are different. A positional indicator may be a universalindicator of options available through a particular type of user input,such as a movement of the rotatable input mechanism. Rather thandisplaying positions within a particular context, such as editing acertain feature or displaying data from a particular application, apositional indicator shows the user positions available through a typeof user input, no matter the particular context in which the user inputis being used. This better indicates to the user which user input shouldbe used for this functionality. In some embodiments, a positionalindicator is displayed on the display at a position adjacent to the userinput for which it is used (e.g., next to the rotatable input mechanismto indicate positions accessible by moving the rotatable inputmechanism).

A positional indicator (e.g., positional indicator 1544) may beresponsive to one or more inputs. For example, as shown in FIG. 15, thepositional indicator 1544 may indicate options available through amovement of the rotatable input mechanism. As described above, the usermay scroll through the available options using movement of the rotatableinput mechanism. However, a user may also wish to scroll through theavailable options using a second type of input, such as a contact (e.g.,a swipe) on the touch-sensitive display. In some embodiments, a userviewing screen 1530 may swipe the touch-sensitive display in a differentdirection than the swipe used for removing a visual indication of afirst element of the clock face for editing and visually indicating asecond element of the clock face for editing (e.g., a downward swipe onthe display). For example, to scroll through the available options shownin FIG. 15, the user may swipe in a substantially horizontal direction(e.g., swipe 1556) to scroll through editable aspects (e.g., with swipesmoving left-to-right resulting in scrolling through the sequence ofeditable aspects in one direction, and swipes moving right-to-leftresulting in scrolling through the sequence of editable aspects in adifferent direction, as depicted by updating the paging affordance1538). In this example, the user may swipe in a substantially verticaldirection (e.g., perpendicular to swipe 1556) to scroll throughavailable options (e.g., with swipes moving downwards resulting inscrolling through the sequence of available options in one direction,and swipes moving upwards resulting in scrolling through the sequence ofavailable options in a different direction, as depicted by updating thepositional indicator 1544). In some embodiments, the user may swipe thedisplay at or near the location of the displayed positional indicator toscroll through the sequence of available options.

In some embodiments, upon detecting the swipe, the device may update anindicator of position (e.g., an indicator of position along a series ofpositions that indicates a position of a currently selected option forthe editable aspect along a series of selectable options for theeditable aspect of the visually indicated element of the clock face) toindicate a second position along the series. In some embodiments, upondetecting the swipe, the device may edit an aspect of the visuallyindicated element of the clock face. In some embodiments, the device mayvisually distinguish the positional indicator (e.g., by changing acolor, size, shape, animation, or other visual aspect) based on the typeof input used to scroll the indicator. For example, in some embodiments,in response to detecting a movement of the rotatable input mechanism,the device may display the positional indicator in a first color (e.g.,green), and in some embodiments, in response to detecting a swipe, thedevice may display the positional indicator in a second color differentfrom the first color (e.g., white).

In clock face edit mode depicted on screen 1560, the user may be able tocycle through different types of information from the weatherapplication, or change the application from which the information isdrawn. In this case, the user moves rotatable input mechanism usingmovement 1568, which causes device 1500 to display screen 1570. Thisupdates complication 1536 to display the current date, which is obtainedfrom a calendar application. This option is indicated within positionalindicator 1544 by line 1572. Note that paging affordance 1538 stillindicates the second position because the user is still engaged inediting complications, the second editable aspect of this clock face. Adetermination that the contact has a characteristic intensity above apredetermined threshold may be user to distinguish the contact fromother gestures, such as a tap or the beginning of a swipe.

Having finished editing the clock face, the user may now exit clock faceselection mode and display the edited clock face on the display. In someembodiments, this may be done by detecting a user contact with acharacteristic intensity above an intensity threshold. In accordancewith a determination that the characteristic intensity is above theintensity threshold, the device may exit clock face edit mode and ceaseto visually distinguish the displayed clock face for editing (e.g., byincreasing the size of the displayed clock face). In some embodiments,in accordance with a determination that the characteristic intensity isabove the intensity threshold, the device may save this edited clockface as a new clock face that is accessible through clock face selectionmode (described below). In accordance with a determination that thecharacteristic intensity is not above the intensity threshold (where theclock face includes an affordance representing an application, and wherethe contact is on the affordance representing the application), thedevice may launch the application represented by the affordance.

In some embodiments, the device may have a rotatable and depressibleinput mechanism (e.g., 506), and in response to detecting a depressionof the rotatable and depressible input mechanism, the device may exitclock face edit mode, display the currently edited clock face, and/orsave the currently edited clock face for later user selection, asdescribed above.

FIG. 15 illustrates an exemplary embodiment of clock face edit mode, buta number of other potential embodiments are possible within the scope ofthe techniques described herein. For example, in FIG. 15, an element wasindicated for editing by visibly distinguishing an outline around theelement (e.g., by displaying a visible outline, or by distinguishing apre-existing outline already visible around the element), as illustratedby outlines 1534 and 1564. In some embodiments, the outline may beanimated to depict a rhythmic expansion and contraction (e.g., animationsimilar to pulsing or breathing). In some embodiments, the elementindicated for editing itself may be animated to depict a rhythmicexpansion and contraction. In some embodiments, the element may beanimated to depict flashing. In some embodiments, a color of the elementmay be changed (e.g., a change in color and/or intensity). Any or all ofthese indications may be used to visually indicate the element that iscurrently editable.

As shown in FIG. 15, movement of a rotatable input mechanism may beemployed as the user input for editing an aspect of the elementindicated for editing. In some embodiments, if an outline is used toindicate the currently editable element, the outline may disappear whenthe rotatable input mechanism is being moved, and reappear when themovement stops. In this way, the user is able to see what the editedelement will look like on the clock face as a whole, without anypossible obstruction or distraction from the outline.

In some embodiments, in response to detecting the movement, the devicemay change a color of the element. This could include, e.g., changing acolor of a clock face background (e.g., substituting a color if theclock face background is a particular color, or selecting a differentimage if the clock face background includes an image), changing a colorof part or all of a seconds hand (if included on the clock face),changing a color of an hour and/or minute indication, and/or changing acolor of a number or colon in the display of a representation of adigital clock. Since a seconds hand is a smaller element than abackground (and therefore may be more difficult for the user toperceive), changing the color of the seconds hand may include ananimated color change. For example, the seconds hand could first changea color of a particular point (e.g., a dot depicted along the secondshand), then propagate this color change in either direction along theseconds hand. Alternatively, the color change could begin at the originof the clock face and propagate outward. Animating a color change,particularly a change of a smaller element of the clock face, may behelpful to draw the user's attention to the color change.

In other embodiments, in response to detecting movement of the rotatableinput mechanism, the device may change an aspect of a complication. Forexample, this could be used to change application data displayed by anapplication complication. In some embodiments, the complication mayindicate a first set of information obtained by an application (e.g.,application data. For example, if the application is a weatherapplication, a set of information could be a forecasted weathercondition, a current temperature, etc.), and upon editing, thecomplication could be updated to indicate a second set of informationfrom the same application (e.g., if the application is a weatherapplication, the display could be edited from showing a currenttemperature to showing current precipitation). In other embodiments,upon editing, the complication could be updated to indicate a set ofinformation from a different application (e.g., if the application is aweather application, the display could be edited from showing weather toshowing data from a calendar application, as illustrated by complication1536).

In other embodiments, in response to detecting movement of the rotatableinput mechanism, the device may change an aspect of display density. Forexample, as illustrated in FIG. 15, this could be used to edit thenumber of visible divisions of time (e.g., the number of displayed hourand/or minute indications, such as numbers 1-12 or other marks/symbolspositioned along the clock face at the hour positions). In response todetecting movement of the rotatable input mechanism, the device mayincrease or decrease the number of visible divisions of time. Asillustrated on screens 1530, 1550, and 1560, this could involve changingthe number of visible divisions (e.g., from 4 to 12) and/or changing thenumber of numerical/symbolic hour indications (e.g., from 0 to 4).

In some embodiments, as illustrated in FIG. 15, an indicator ofpositions along a series of positions may be displayed (e.g., positionalindicator 1544). In response to detecting movement of the rotatableinput mechanism, the device may update the indicator from indicating afirst to indicating a second position along the series of positions. Insome embodiments, the indicated position may reflect a currentlyselected option for the currently editable aspect along a series ofselectable options for the currently editable aspect. As describedabove, in some embodiments, the indicator is displayed on the display ata position adjacent to the rotatable input mechanism, therebystrengthening the user's association between the indicator and theinput. In some embodiments, if the currently editable aspect is color,the device may display a positional indicator that includes a series ofcolors, such that the currently selected color option matches the colorof the position currently indicated by the positional indicator (e.g.,the color could be a similar or identical color). In some embodiments,the number of positions displayed in a position indicator increases ordecreases depending on the number of options for the currently selectededitable aspect.

In some embodiments, upon reaching the last position indicated by thepositional indicator, the device may provide an indication to the userthat the last option has been displayed. For example, the device maydepict a dimming of one or more of the selected element, an outlinearound the selected element, and the positional indicator. In someembodiments, the device may animate one or more of the selected element,an outline around the selected element, and the positional indicator toexpand and contract (e.g., like a rubber band). In some embodiments, thedevice may animate one or more of the selected element, an outlinearound the selected element, and the positional indicator to move on thedisplay (e.g., by bouncing). These features may be advantageous toprovide an indication to the user that the last option in the series ofoptions has been reached.

In some embodiments, a user may select the element on the clock face forediting by contacting the touch-sensitive display at the position of thedisplayed element. In other embodiments, the element may be selected byswiping the touch-sensitive display, or rotating the rotatable inputmechanism. Regardless of the input, selecting a second element forediting may involve removing a visual indication from the previouselement and visually indicating a second element for editing (visuallyindicating may include any or all of the techniques described above).

In some embodiments, if the element selected for editing is indicated byan outline around the element, changing an element for editing couldinvolve translating the outline on-screen away from the first elementand/or translating a visible on-screen in a continuous on-screenmovement towards the second element until the outline is displayedaround the second element.

As illustrated in FIG. 15, clock face edit mode allows the user to altermultiple editable aspects of the clock faces described herein. In someembodiments, in response to detecting a swipe on the touch-sensitivedisplay (e.g., swipe 1556), the device may select a second element ofthe clock face for editing, which in response to detecting another userinput (e.g., a movement of the rotatable input mechanism), may beedited. This allows the user to cycle through different editable aspectsof the displayed clock face, such as colors, number and/or type ofcomplications, and display density.

A user may wish to match a color of a displayed clock face to an image.In some embodiments, the device may receive a user input, and inresponse to receiving the user input, the device may enter a colorselection mode. While in the color selection mode, the device mayreceive data representing an image, and in response to receiving thedata, the device may select a color of the image and update a displayedclock face by changing a color on the clock face (e.g., a clock facebackground, hour and/or minute indication, and/or seconds hand) to matchthe color of the image. In some embodiments, the color selected may havethe greatest prevalence of the colors in the image. This allows the userto further customize a clock face to display a designated color. Forexample, if the user is wearing a blue shirt, the user could take animage of the blue shirt and match the color of the clock face to theshirt. In some embodiments, the data representing the image may beobtained from an image stored on the device, an image stored on anexternal device in wireless communication with the device (e.g., Wi-Fi,Bluetooth™, near field communication (“NFC”), or any of the othercellular and/or other wireless communication techniques describedherein), or an image taken using a camera on the device, such as cameramodule 143 or optical sensor 164.

Having described various context-specific user interfaces and methods ofuser editing thereof, attention is now directed to methods of selectinga context-specific user interface shown in FIGS. 16A-C. Numerousindividual context-specific user interfaces are possible using thetechniques described here. A user may wish to select a particular clockface (e.g., from a saved library of clock faces) or make a new one,depending on a particular context. For example, a user may wish todisplay a particular clock face during working hours to project aprofessional appearance, but change the clock face during the weekend toreflect an interest (such as astronomy, exercise, or photography). Auser may wish for quick access to a stopwatch in one context, whiledesiring an indication of daytime hours in another.

FIG. 16A shows exemplary context-specific user interfaces that may beoperated on device 1600. Device 1600 may be device 100, 300, or 500 insome embodiments. The electronic device has a touch-sensitive display(e.g., touchscreen 504) configured to detect the intensity of contacts.Exemplary components for detecting the intensity of contacts, as well astechniques for their detection, have been referenced and described ingreater detail above.

Device 1600 displays user interface screen 1602, which includes clockface 1604. In this example, the user wishes to switch from clock face1604 to a different clock face. The user contacts the touch-sensitivedisplay of device 1600 with touch 1606. Touch 1606 has a characteristicintensity above an intensity threshold, which prompts device 1600 toenter a clock face selection mode, shown on screen 1610. Clock faceselection mode allows the user to select a clock face.

Device 1600 indicates that the user has entered clock face selectionmode by visually distinguishing the clock face. This is shown on screen1610. Screen 1610 visually distinguishes that the user has entered clockface selection mode by centering reduced size clock face 1612 on thedisplay (reduced size clock face 1612 is based on clock face 1604). Thisindicates to the user that the user is in clock face selection modewhile giving the user an indication of what the clock face will looklike when displayed at full size.

Screen 1610 also includes paging affordance 1614. As described above,paging affordances may indicate where the user is within a sequence ofoptions, as well as how many options are available in the sequence.Paging affordance 1614 indicates to the user that clock face 1612 is thefirst in a series of three selectable clock faces and/or clock faceoptions (e.g., an option to add a new clock face or randomly generate aclock face, as described below). In clock face selection mode, a pagingaffordance may indicate a currently centered clock face and/or clockface option, a position of the currently centered clock face and/orclock face option within a sequence of clock faces and/or clock faceoptions, and a total number of available clock faces and/or clock faceoptions. This helps the user navigate the clock faces and clock faceoptions.

Screen 1610 also includes a partial view of a second clock face, asshown by a partial view of second clock face 1616. In some embodiments,when the device is in clock face selection mode, the device may includea display a partial view of another clock face, or clock face option,particularly the clock face or clock face option next in the sequence(e.g., as indicated by the paging affordance). This further helps theuser understand that additional options are available. In otherembodiments, only one clock face is displayed at any time.

Clock face selection mode may be used to select a clock face for displayas a context-specific user interface, or to select a clock face forediting. Therefore, in some embodiments, when a clock face such as clockface 1612 and/or clock face 1616 is centered on the display, a user maycontact the displayed clock face on the touch-sensitive display toselect the centered clock face for editing and enter into clock faceediting mode (as described above in reference to FIG. 15). In someembodiments, clock face editing mode is entered when the contact has acharacteristic intensity above an intensity threshold. Coupling clockface edit and selection modes in a single interface allows the user toselect different clock faces and edit them quickly and easily.

A user may select a different clock face (for editing or for display asa context-specific user interface) by swiping. Device 1600 detects aswipe on the touch-sensitive display (e.g., swipe 1618). In response todetecting swipe 1618, device 1600 displays screen 1620. Screen 1620includes second clock face 1616 centered on the display (part of secondclock face 1616 was depicted on screen 1610). Screen 1620 also showspaging affordance 1614, which has been updated to indicate that thecurrently centered clock face 1616 is second within the sequence ofclock faces and/or clock face options. Also shown is a partial viewclock face 1612. This helps the user understand the sequence of clockfaces, similar to a paging affordance but with the added benefit ofdisplaying a partial view of the clock faces for user recognition.

To select clock face 1616, the user contacts the touch-sensitive displayon clock face 1616 (e.g., touch 1622). In response to detecting touch1622, device 1600 exits the clock face selection mode and displaysscreen 1630. Screen 1630 includes full-sized clock face 1632, which isbased on clock face 1616. In this example, clock face 1632 is acontext-specific user interface similar to those described in referenceto FIGS. 11A-C and includes affordance 1634 indicating the time of day,user interface object 1636 (a sinusoidal wave indicating a path of theSun through the day), and affordance 1638 representing the Sun.

As described above and illustrated in FIG. 16A, a user may select aclock face from a plurality of clock faces in the device's clock faceselection mode. In some embodiments, at least a first and a second clockface are shown when the device is in clock face selection mode. Theseclock faces may be shown in sequence, but at a reduced size. In someembodiments, one clock face is centered on the display at any time, andthe one or more additional clock faces on the display are shown inpartial view, as depicted by partial views of clock faces 1612 and 1616.Centering a clock face may include includes translating the prior clockface in the sequence on-screen and displaying the prior clock face inpartial view. In other embodiments, only a single clock face isdisplayed on the device at any one time (i.e., no partial views).

In some embodiments, centering a clock face on the display includessimulating a movement of the clock face towards the user on the display,as if it is approaching the user. This helps draw the user's attentionto the clock face while conveying to the user a sense of the clock facesequence.

As depicted by screen 1620, device 1600 may display multiple availableclock faces and/or clock face options in a sequence for selection by theuser. A user may wish to re-order one or more clock faces within thesequence. Therefore, device 1600 may provide a clock face rearrangementmode to allow the user to select a particular clock face and change itsorder within the sequence of available clock faces and/or clock faceoptions. In some embodiments, a user may contact the touch-sensitivedisplay on a clock face (e.g., clock face 1616) and maintain the contactbeyond a threshold interval (e.g., a “press and hold”-type user input).In response to detecting the contact, and in accordance with adetermination that the contact exceeds a predetermined threshold, device1600 may enter a clock face rearrangement mode. Device 1600 mayhighlight, outline, animate, or otherwise visually distinguish the clockface to indicate to the user that device 1600 has entered clock facerearrangement mode, and that the clock face has been selected forrearrangement. In some embodiments, while continuing to receive the usercontact, device 1600 may detect movement of the user contact from afirst position within the sequence of displayed clock faces and/or clockface options to a second position, which is different from the firstposition, without a break in contact of the user contact on thetouch-sensitive display. In other embodiments, the contact comprisingthe movement from a first position within the sequence of displayedclock faces and/or clock face options to a second position, which isdifferent from the first position, without a break in contact of theuser contact on the touch-sensitive display may be a separate contactsubsequent to entry into clock face rearrangement mode. In response todetecting the contact at the second position, device 1600 may translatethe clock face on-screen from the first position to the second position.Optionally, other partial or complete clock faces and/or clock faceoptions on the display may be moved accordingly to accommodate the newposition of the user-selected clock face. A user may then cease thecontact to select the second position as the new position for the clockface within the sequence of displayed clock faces and/or clock faceoptions. In some embodiments, device 1600 may exit clock facerearrangement mode in response to detecting the break in contact on thetouch-sensitive display after the position of at least one clock facehas been rearranged. In other embodiments, in response to detecting auser input subsequent to the break in contact on the touch-sensitivedisplay (e.g., a depression of a rotatable and depressible inputmechanism such as 506), device 1600 may exit clock face rearrangementmode. In some embodiments, upon exiting clock face rearrangement mode,device 1600 may re-enter clock face selection mode.

In addition to selecting an existing context-specific user interface, auser may also wish to add a new one. FIG. 16B illustrates an exemplaryuser interface for generating a new clock face. Shown on FIG. 16B isdevice 1600, which displays screen 1640. Screen 1640 displays clock face1642 and paging affordance 1644, which indicates to the user that thecurrently centered clock face is the first in a sequence of threeselectable clock faces and/or clock face options. Screen 1640 alsodisplays a partial view of a clock face generation affordance (e.g.,1646).

In this example, the user swipes the display (e.g., swipe 1648), and inresponse to detecting the swipe, device 1600 displays a full view ofclock face generation affordance 1646 centered on screen 1650. In someembodiments, as depicted by affordance 1646, a clock face generationaffordance may include a plus sign (or other text and/or symbol) toconvey to the user that, upon activation of affordance 1646, device 1600will generate a new clock face.

Note that screen 1650 also displays a partial view of previouslydisplayed clock face 1642. This partial view of 1642 and updated pagingaffordance 1644 (updated to indicate that clock face generation is thesecond available user interface in the sequence) help orient the userwithin the sequence of available clock faces and/or clock face options.Further note that the partial view of clock face generation affordance1646 on screen 1640 indicates to the user that a swipe will centeraffordance 1646 on the display (e.g., as displayed on screen 1650) foruser activation.

A user may activate affordance 1646, for example by contactingaffordance 1646 on the touch-sensitive display (e.g., touch 1652). Inresponse to detecting the contact, device 1600 displays screen 1660,which includes newly generated clock face 1662 centered on the display.As shown on screen 1660, new clock face 1662 includes affordance 1664,which displays the current date (e.g., obtained from a calendarapplication), and affordance 1666, which displays the current weatherconditions (e.g., obtained from a weather application).

In response to detecting an activation of affordance 1646, in someembodiments, the device remains in clock face selection mode aftercentering the displayed new clock face. In other embodiments, uponcentering the newly generated clock face on the display, the deviceenters into clock face edit mode, as described above. This allows theuser to edit one or more aspects of the newly generated clock face. Insome embodiments, the device exits clock face selection mode and centersthe new clock face as a full-size clock face on the display.

It is to be appreciated that, while new clock face 1662 depicts arepresentation of an analog clock, any of the context-specific userinterfaces described herein (with any of the optional features describedherein) may be a new clock face generated in response to activating theclock face generation affordance. In some embodiments, a new clock facemay have a different customizable aspect, as compared to existing clockfaces on the device. For example, if the user already has a clock facethat includes a blue seconds hand, the device may generate a new clockface that includes a red seconds hand. This helps the user explore theoptions available for context-specific user interfaces described herein,thus enhancing the user interface by increasing variety.

In addition to selecting an existing context-specific user interface orgenerating a new context-specific user interface, a user may also wishto create a random context-specific user interface. FIG. 16C illustratesan exemplary user interface for generating a random clock face. Shown onFIG. 16C is device 1600, which displays screen 1670. Screen 1670displays clock face 1672 and paging affordance 1674, which indicates tothe user that the currently centered clock face is the first in asequence of three selectable clock faces and/or clock face options.Screen 1670 also displays a partial view of a random clock facegeneration affordance (e.g., 1676).

In this example, the user swipes the display (e.g., swipe 1678), and inresponse to detecting the swipe, device 1600 displays a full view ofrandom clock face generation affordance 1676 centered on screen 1680. Insome embodiments, as depicted by affordance 1676, a random clock facegeneration affordance may include a question mark (or other text and/orsymbol, such as the letter “R”) to convey to the user that, uponactivation of affordance 1676, device 1600 will generate a random clockface.

Note that screen 1680 also displays a partial view of previouslydisplayed clock face 1672. The partial view of 1672, along with updatedpaging affordance 1674 (updated to indicate that random clock facegeneration is the second available user interface in the sequence),helps orient the user to the sequence of clock faces and/or optionsavailable in the sequence. Further note that the partial view of randomclock face generation affordance 1676 on screen 1670 indicates to theuser that a swipe will center affordance 1676 on the display (e.g., asdisplayed on screen 1680) for user activation.

A user may activate affordance 1676, for example by contactingaffordance 1676 on the touch-sensitive display (e.g., touch 1682). Inresponse to detecting the contact, device 1600 displays screen 1690,which includes randomly generated clock face 1692 centered on thedisplay. As shown on screen 1690, new clock face 1692 includesaffordance 1694, which represents an affordance for launching astopwatch application, and affordance 1696, which displays the currenttemperature (e.g., obtained from a weather application).

In response to detecting an activation of affordance 1676, in someembodiments, the device remains in clock face selection mode aftercentering the displayed random clock face. In other embodiments, uponcentering the randomly generated clock face on the display, the deviceenters into clock face edit mode, as described above. This allows theuser to edit one or more aspects of the randomly generated clock face.In some embodiments, the device exits clock face selection mode andcenters the random clock face as a full-size clock face on the display.

It is to be appreciated that, while random clock face 1692 depicts arepresentation of an analog clock, any of the context-specific userinterfaces described herein (with any of the optional features describedherein) may be a random clock face generated in response to activatingthe random clock face generation affordance.

In some embodiments, the random clock face may be different from any ofthe other clock faces available in clock face selection mode. The devicemay accomplish this in multiple ways. In some embodiments, the devicemay randomly generate a random clock face, and then check the randomclock face against the other stored clock faces to ensure that it isdifferent. In other embodiments, the device may generate a random clockface and rely on the inherent probability that it will be different fromthe stored clock faces, given the sheer number of potential clock facesmade available by the techniques described herein.

In some embodiments, upon displaying the random clock face, the devicemay display a user prompt for generating a second random clock face.This allows the user to randomly generate another clock face if the userdoes not like the particular type of context-specific user interfaceand/or customized features of the random clock face. In someembodiments, the random clock face generation affordance may depict,e.g., a slot machine or other indication of a user prompt for generatinga second random clock face, to provide this feature.

In addition to centering a clock face on the display for selection, thedevice may also highlight the centered clock face in one or more ways.For example, in some embodiments, the centered clock face may bedisplayed by visibly distinguishing an outline around the centered clockface (e.g., by displaying a visible outline, or by distinguishing apre-existing outline already visible around the clock face), asillustrated by 1612, 1622, 1642, and 1672. In some embodiments, theoutline may be animated to depict a rhythmic expansion and contraction(e.g., animation similar to pulsing or breathing). In some embodiments,the centered clock face itself may be animated to depict a rhythmicexpansion and contraction. In some embodiments, the centered clock facemay be animated to depict flashing. In some embodiments, a color of thecentered clock face may be changed (e.g., a change in color and/orintensity). Any or all of these indications may be used to visuallyindicate that the centered clock face is currently selectable.

As described above, the techniques presented herein related to selectionof a clock face may be applied to any of the context-specific userinterfaces of the present disclosure. A user may wish to display a clockface with an image, such as a user photo or other image file, as thebackground (see, e.g., the context specific user-interfaces, components,and techniques described in reference to FIGS. 12, 24, and 39). It istherefore desirable to provide a user interface that allows the user toselect an image from a set of multiple images (e.g., from an imagefolder or photo album). A user may also wish to customize the appearanceof a selected image. For example, the image may have been taken on adevice with a different resolution or aspect ratio, and the user maywish to customize the look of the image to fit a device with a reducedsize display. As such, it is also desirable to provide a user interfacethat allows for quick customization of a selected image (e.g., bycropping, zooming, and/or re-centering the image) to fit a reduced sizedisplay. Advantageously, the techniques described below allow for anefficient interface that provides both of these functionalities, therebyimproving battery life and reducing processor power by lessening thenumber of user inputs required to select and edit images.

FIG. 16D shows additional exemplary user interfaces that may be operatedon device 1600. In FIG. 16D, device 1600 displays screen 1603, which,similar to screen 1610 in FIG. 16A, includes reduced size clock face1605, paging affordance 1609, and a partial view of clock face 1607. Inresponse to detecting user swipe 1611, device 1600 displays screen 1613,which includes a partial view of clock face 1605, an updated pagingaffordance 1609 (updated to indicate to the user that the clock facerepresented by 1607 is the second of three available clock faces orclock face options), and reduced size clock face 1607.

In this example, reduced size clock face 1607 represents a user image bydisplaying a reduced size version of the user image. While 1607 shows asingle, reduced size image that represents the user image, anyrepresentation of an image could be displayed, such as a set of multipleimages (e.g., a representation of a photo album), or an affordance thatrepresents an image and/or photo album via text, such as a text thatreads “Photo,” “Album,” or the like. These representations indicate tothe user that this option, when selected, displays a clock face with abackground image along with an indication of the time of day and/ordate. In some embodiments, more than one image, and/or more than onerepresentation of an image, may displayed.

To select clock face 1607, the user contacts the touch-sensitive displayon clock face 1607 (e.g., touch 1615). In response to detecting touch1615, device 1600 exits the clock face selection mode and displaysscreen 1617. Screen 1617 displays a full-sized clock face that includesbackground 1619, affordance 1621 indicating a time of day, andaffordance 1623 indicating a date or day of the month. Background 1619may be based on the image represented by 1607. For example, it may be alarger version of the same image (e.g., if 1607 displays a singleimage), a larger version of an image thumbnail displayed as part of analbum (e.g., if 1607 displays more than one image, as described below),or it may be an image represented via text by 1607. As used herein, abackground “based on” an image may refer to a background that is basedon at least the first image, i.e., additional images may be displayed.In some embodiments, affordance 1621 and/or 1623 may be generated bymodifying in appearance a subset of pixels constituting background 1619(e.g., as described in reference to FIG. 12, such as by color blurring,blending, gradient, etc.).

FIG. 16E illustrates an alternative technique for selecting animage-based clock face. Rather than immediately selecting a single imagefor display (e.g., as background 1619), a user may wish to first accessa set of multiple images (e.g., a photo album). FIG. 16E begins with thesame user interfaces and inputs described in relation to screens 1603and 1613. However, in response to a user selection of the image-basedclock face option (e.g., touch 1615 on reduced size clock face 1607),device 1600 instead displays screen 1625, which in this example includesrepresentations of nine different images, including representation 1627,which represents the image on which background 1619 is based.

Screen 1625 represents a set of images (e.g., from a user photo album)in a grid-type layout with rows and columns. Any type of layout may beused. In some embodiments, screen 1625 may display a composite imagecomprising representations associated with individual images, such asphotos from a photo album. These representations may include indications(e.g., labels) and/or visual representations (e.g., thumbnail images) ofthe corresponding images. The user may select the image associated withrepresentation 1627 by contacting the displayed representation withtouch 1629. In response to detecting touch 1629, device 1600 displaysscreen 1617, as described above.

In some embodiments, the user may have the option of pre-selecting apreference as to whether device 1600 displays a single image, asillustrated by FIG. 16D, or multiple images, as illustrated by FIG. 16E.In some embodiments, in response to a user selection of an image-basedclock face (e.g., touch 1615), device 1600 may provide a user prompt forviewing a single image or multiple images. A user may then provide aninput (e.g., a touch on the touch-sensitive display) to select theappropriate option.

Once an image has been selected for the background of the clock face, auser may wish to modify the image or replace it with a different image.Advantageously, both functionalities may be provided from a single userinterface using the zoom/crop operations described below. As an example,FIGS. 16F & 16G illustrate how simple rotations of a rotatable inputmechanism in different directions may allow the user to navigateseamlessly from a single image to image modifications (e.g., zooming,cropping, and the like), or from a single image back out to a photoalbum (e.g., for selecting a different image). It will be appreciatedthat other user inputs, such as various touch gestures, mayalternatively or additionally be employed.

As illustrated in FIG. 16F, while screen 1617 is displayed, the user maymove a rotatable input mechanism is a first direction of rotation (e.g.,movement 1631) to crop the image on which background 1619 is based. Inresponse to detecting movement 1631, device 1600 displays screen 1633with image 1635, a cropped image based on background 1619. Image 1635may be generated, for example, by modifying background 1619 in one ormore of the following ways: removing one or more outer portions ofbackground 1619, increasing the magnification of at least a portion ofbackground 1619 (e.g., zooming), or altering the aspect ratio ofbackground 1619. This allows the user to quickly crop an image, forexample to improve the appearance of the image on a reduced-sizedisplay.

In some embodiments, the amount of cropping used to generate image 1635based on background 1619 is proportional to the degree, amount, speed,and/or number of rotations of the rotatable input mechanism. In otherembodiments, the amount of cropping used to generate image 1635 based onbackground 1619 is not proportional to the degree, amount, speed, and/ornumber of rotations of the rotatable input mechanism. Any model formapping a movement of a rotatable input mechanism to the amount or speedof cropping may be used, such as those described in reference toscrolling in U.S. patent application Ser. No. 14/476,700, “Crown Inputfor a Wearable Electronic Device,” filed Sep. 3, 2014, which is herebyincorporated by reference in its entirety. For example, acceleration,velocity, or the like may be used to determine the amount of speed ofscaling of the cropped image.

Other image manipulations are possible using other user inputs. Forexample, as illustrated in FIG. 16F, the user may provide a drag gesture(e.g., drag 1637) on screen 1633 to re-center or translate image 1635 onthe display. In response to detecting drag 1637, device 1600 displaysscreen 1639 with image 1641. Image 1641 is based on a translation of1635 on the display. The degree and/or orientation of the translationmay be based at least in part on the amount, direction, and/or speed ofdrag 1637. Other user inputs are possible, such as taps or othercontacts on the touch-sensitive display. For example, the user may tapor double-tap the image, and, in response, device 1600 may re-center theimage based at least in part on the location of the received tap(s).

Once the user is satisfied with image 1641, it may be selected as thenew background by a touch input, such as touch 1643. Touch 1643 has acharacteristic intensity above an intensity threshold (which may be thesame or different threshold described above in reference to touch 1606),which prompts device 1600 to display user prompt 1645 asking the user toconfirm setting image 1641 as the background. In response to detecting auser confirmation of image 1641 (e.g., by touch 1647 on a “YES”affordance), device 1600 displays screen 1649, which includes image 1641as the background and affordances 1621 and 1623. In other embodiments,device 1600 may forego displaying user prompt 1645 and instead displayscreen 1649 in response to touch 1643. If touch 1643 has acharacteristic intensity that is not above the intensity threshold,device 1600 may forego displaying screen 1649 and/or modify image 1641in appearance, e.g., as described above.

In some embodiments, affordances 1621 and/or 1623 may be modified inappearance, compared to when they are displayed on background 1619,based on the different appearance of 1641 compared to 1619. For example,they may constitute a modification of a subset of pixels of a differentimage, or a different subset of pixels from the same image (e.g., 1641vs. 1619). In other embodiments, affordances 1621 and/or 1623 may havethe same appearance on both screens.

FIG. 16G illustrates an exemplary technique for allowing the user toselect a different image. While screen 1617 with background 1619 isdisplayed, the user may move a rotatable input mechanism is a seconddirection of rotation (e.g., movement 1651). In some embodiments,movement 1651 may have a direction of rotation opposite that of movement1631. In response to detecting movement 1651, device 1600 displaysscreen 1625, which as described above represents a set of images (e.g.,from a user photo album). The user may select the image corresponding torepresentation 1653 (which as described above may be an image such as athumbnail or an indication such as a label) by touch 1655.

In response to detecting touch 1655, device 1600 displays screen 1657,which includes a background based on image 1659. Similar to FIG. 16F,the user may crop, zoom, or otherwise modify image 1659 through one ormore rotations of the rotatable input mechanism or one or more touchgestures. Similar to FIG. 16F, the user may touch screen 1657 with touch1661 to select image 1659 as the background image. Touch 1661 has acharacteristic intensity above an intensity threshold (which may be thesame or different threshold described above in reference to touch 1606or 1643), so in accordance with a determination that touch 1661 has acharacteristic intensity above the intensity threshold, device 1600displays user prompt 1663 to confirm setting image 1659 as thebackground. In response to detecting a user confirmation of image 1659(e.g., by touch 1663 on a “YES” affordance), device 1600 displays screen1667, which includes image 1659 as the background and affordances 1669and 1671. In other embodiments, device 1600 may forego displaying userprompt 1663 and instead display screen 1667 in response to touch 1661.If touch 1661 has a characteristic intensity that is not above theintensity threshold, device 1600 may forego displaying screen 1667and/or modify image 1659 in appearance, e.g., as described above. Insome embodiments, affordances 1669 and 1671 may be the same asaffordances 1621 and 1623, respectively. In other embodiments,affordances 1669 and 1671 may be distinct from affordances 1621 and1623, respectively, e.g., as modifications of a subset of pixels of adifferent image (image 1659 vs. 1619).

The techniques described above allow for a single user interface forselecting and modifying images to generate an image-basedcontext-specific user interface of the present disclosure. Providing asingle user interface for these functionalities reduces the number ofuser inputs required to accomplish these tasks, thereby reducing batteryconsumption and processor power. While these operations are illustratedin FIGS. 16F & 16G using the movement of a rotatable input mechanism(e.g., 506) and specific touch gestures, it will be appreciated thatother combinations of user inputs such as touch gestures may be used.

In some embodiments, the user may access clock face edit mode and clockface selection mode through a shared interface. For example, a contactwith a characteristic intensity above the intensity threshold may causethe device to enter clock face selection mode. In this example, screen1510 in FIG. 15 may represent clock face selection mode, with a pagingaffordance that indicates the currently selected clock face within asequence of selectable clock faces and/or clock face options. Uponentering clock face selection mode, in some embodiments, a secondcontact with a characteristic intensity above the intensity thresholdmay cause the device to enter into the clock face edit mode and selectthe currently centered clock face for editing. In other embodiments,upon entering clock face selection mode, the device may display anaffordance representing clock face edit mode. Upon detecting a contacton the displayed affordance, the device may enter into the clock faceedit mode and select the currently centered clock face for editing.These features help tie the context-specific user interface selectionand editing functionalities into a single interface that isuser-friendly and intuitive.

3. Additional Functionalities for Context-Specific User Interfaces

A user may wish for additional functionalities in a context-specificuser interface that may be applied to the user interfaces describedabove. For example, a user may wish to set reminders, launchapplications, and view the time at a designated location. Suchfunctionalities are not limited to particular user interfaces describedherein, but rather may be generally applied to any or all of them. Thefollowing functionalities are generalizable features that may beincorporated into any of the context-specific user interfaces describedherein. While a specific functionality may be described in reference toa particular context-specific user interface below, this is in no wayintended to be limiting.

FIG. 17A shows exemplary context-specific user interfaces that may beoperated on device 1700. Device 1700 may be device 100, 300, or 500 insome embodiments. In some embodiments, the electronic device has atouch-sensitive display (e.g., touchscreen 504) and a rotatable inputmechanism (e.g., 506 or 1540).

In this example, a user wants to set a reminder for 6:00 (this may be areminder for 6:00 at a specific day or a general reminder for 6:00 everyday). Device 1700 displays user interface screen 1702. Screen 1702depicts a clock face similar to those described in reference to FIGS.11A-C and includes affordance 1704, which indicates the time of day, anda sinusoidal wave indicating a path of the Sun through the day. Screen1702 further includes affordance 1708, which as described in FIG. 11Aindicates a current time of day by its position along the sinusoidalwave (10:09).

A user may contact the display, which then prompts the device to enterinto a user interaction mode. User interaction mode provides the useradditional interactions available within the user interface, such assetting a user reminder. Once in user interaction mode, a user moves therotatable input mechanism (e.g., movement 1708), and in response todetecting the movement, device 1700 displays screen 1710. Screen 1710displays a non-current time of day (6:00), as indicated by affordance1712 and the position of affordance 1714 along the sinusoidal wave. Theuser may use movement 1708 to scroll through times of day until adesignated time is displayed (in this case 6:00) so the user can set areminder for the designated time of day.

The user contacts the display at affordance 1714 (e.g., touch 1716), andin response to detecting the contact, device 1700 sets a reminder forthe indicated time of day (6:00). This allows the user to set adesignate a time of day for a user reminder.

FIG. 17B shows device 1700 at a later time of day (11:00). Device 1700displays screen 1720. Screen 1720 includes affordance 1722, whichindicates the current time, and affordance 1724, which indicates acurrent time of day by its position along the sinusoidal wave. As shownin FIG. 11B, in this context-specific user interface, a user may contactaffordance 1724 (e.g., touch 1726) to view user interface objectsrepresenting dawn, dusk, sunrise, and sunset.

In response to detecting the contact, device 1700 displays screen 1730.Screen 1730 includes affordance 1732, which indicates the current timeof day, and affordance 1734, which also indicates the current time ofday by its position along sinusoidal wave 1736. Line 1738 depicts theboundary between the daytime and nighttime portions of the display. Asdescribed above, screen 1730 includes user interface objects 1740(representing a time of dawn), 1742 (representing a time of sunrise),1744 (representing a time of sunset), and 1746 (representing a time ofdusk).

Importantly, screen 1730 also displays affordance 1748. Affordance 1748is a visual reminder of the time of day designated by the user (6:00) inFIG. 17A. Thus, the device now displays a user reminder for this time ofday, in this case in response to a user contact on affordance 1724.

In some embodiments, setting the user reminder may include displaying anaffordance representing a user prompt to set an alert for the designatedtime of day. This affordance may include a user interface for settingone or more properties of the alert.

In some embodiments, a user reminder may include a calendar event. Forexample, instead of a user setting the user reminder as described above,the device may import a calendar event from a calendar application.Using the example illustrated in FIG. 17B, affordance 1748 may representa calendar event imported from a calendar application. Importing acalendar event from a calendar application allows the user to track thetime of the calendar event compared with the current time and/or othertimes of interest (e.g., sunrise, sunset, dawn, or dusk). For example,the user may be able to view the time of a tennis match (stored as acalendar event) as part of screen 1730 and thereby gauge how much timeis left before the match is scheduled, or how much time is availablebetween the start of the match and sunset. In some embodiments, the usermay move the rotatable input mechanism (e.g., movement 1708), and inresponse to detecting the movement, the device may snap to the userreminder by visually distinguishing affordance 1748 and/or by updating adisplayed indication of time to indicate the time associated with theuser reminder represented by affordance 1748.

In some embodiments, the user reminder represents a recurring event. Insome embodiments, the time of the user reminder is based on a fixedchronological time. To use FIG. 17B as an example, if the user reminderis a tennis match, it may recur at the same chronological timethroughout the year, but the position of affordance 1748 relative toline 1738 may change throughout the year. This would allow the user todetermine whether sufficient daylight will be present throughout thematch on a given date simply by viewing the position of affordance 1748.In other embodiments, the time of the user reminder is based on a solarcondition (e.g., the amount of daylight or lack thereof). For example, auser reminder may reflect the time of a solar condition, such as aparticular time before sunset, or the time that the sun is at aparticular angle above the horizon. Therefore, if such a user reminderis recurring, the chronological time of the user reminder may vary overtime while still representing the same solar condition, allowing theuser to plan for viewing this solar condition at any time of the year.

The user reminder for the designated time of day may include one or moreoptional features. In some embodiments, the reminder may include avisual alert for the designated time of day. For example, the device maydisplay a visual alert on or before the designated time of day.Alternatively, the device may display at any time a visual affordancethat shows the designated time of day within the context of the currentuser interface. In the example of FIG. 17B, visual affordance 1748 isdisplayed along the sinusoidal wave to help the user understand how farthe designated time of day is from the current time of day.

In some embodiments, the user reminder may include an audio alert forthe designated time of day. For example, the device may play a sound onor before the designated time of day. In some embodiments, the userreminder may include a haptic alert generated on or before thedesignated time of day (e.g., using haptic feedback module 133 andtactile output generator 167). This haptic signal lets the user knowwhen the designated time of day is approaching.

Turning now to FIG. 18A, any or all of the context-specific userinterfaces described herein may include one or more complications. Onetype of complication a user may wish to use is a complication forlaunching an application. For example, the affordance representing thecomplication on the clock face may display a set of information from thecorresponding application. However, a user may wish to view additionalinformation from the application, or launch the full application itself.

FIG. 18A shows exemplary context-specific user interfaces that may beoperated on device 1800. Device 1800 may be device 100, 300, or 500 insome embodiments. In some embodiments, the electronic device has atouch-sensitive display (e.g., touchscreen 504).

Device 1800 displays user interface screen 1802. Screen 1802 includesclock face 1804 and affordances 1806 and 1808, which are displayed ascomplications. Affordances 1806 and 1808 represent applications andinclude a set of information obtained from the correspondingapplication. In this example, affordance 1806 represents a weatherapplication and displays weather conditions obtained from the weatherapplication. Affordance 1808 represents a calendar application anddisplays the current date obtained from the calendar application.Affordance 1806 and affordance 1808 are updated in accordance with datafrom the corresponding application. For example, affordance 1806 isupdated to display current weather conditions obtained from the weatherapplication. Affordance 1808 is updated to display the current dateobtained from the calendar application. For example, these complicationsmay be application widgets updated based on application data.

To launch the weather application, a user contacts the display ataffordance 1806 (e.g., touch 1810). In response, device 1800 launchesthe weather application, which is depicted on screen 1820. Screen 1820shows further weather information, including current weather conditions(e.g., user interface object 1822), an indication of the currentlocation (e.g., user interface object 1824), and an indication of thecurrent temperature (e.g., user interface object 1826).

FIG. 18B also depicts device 1800 displaying screen 1802. As depicted inFIG. 18A, screen 1802 includes clock face 1804 and affordances 1806 and1808, which are displayed as complications.

If a user wishes to launch the calendar application instead of theweather application, the user contacts the display at affordance 1808(e.g., touch 1812). In response, device 1800 launches the calendarapplication, which is depicted on screen 1830. Screen 1830 shows furthercalendar information, including user interface object 1832, whichdepicts the full date, and user interface object 1834, which representsa calendar event (in this case, a meeting at 1).

In some embodiments, a user interface screen may display a complicationthat represents an application and includes a set of informationobtained from the corresponding application. In some embodiments, asillustrated by FIGS. 18A and 18B, a user interface screen may display aplurality of complications that represent applications and include setsof information obtained from a plurality of applications, or a pluralityof sets of information obtained from a single application.

In some embodiments, as described above, a user may move a rotatableinput mechanism to scroll a displayed indication of time forward orbackward. In some embodiments, the device may display two or moreindications of time, and in response to detecting a movement of therotatable input mechanism, the device may update one or more of thedisplayed indications of time and keep another indication of timeconstant. To illustrate using screen 1802 in FIGS. 18A and B as anexample, if affordance 1808 represents an indication of current time(e.g., a digital display), the device may update the displayed clockface in response to detecting the movement of the rotatable inputmechanism while continuing to display the current time with affordance1808. The displayed clock face may be updated, for example, by animatinga clockwise or counter-clockwise movement of one or more clock hands,depending on whether the displayed time is scrolled forward or backward.

In some embodiments, the device may update other displayed complications(e.g., those that do not indicate a time per se) in response todetecting the movement of the rotatable input mechanism. For example, inaddition to updating the time displayed by clock face 1804, the devicemay also update the forecasted or historical weather condition displayedby affordance 1806 to correspond with the time indicated by clock face1804. In these embodiments, the device may forego updating anotherdisplayed complication in response to scrolling the displayed time. Forexample, a displayed stopwatch complication may remain the same whilethe displayed clock face is updated. In some embodiments, a displayedcomplication that is not updated in response to detecting the movementof the rotatable input mechanism may be visually distinguished, such asby changing a hue, saturation, and/or lightness of the displayedcomplication. This allows the user to distinguish which complicationsare updated and which remain constant.

Advantageously, these context-specific user interface methods, which maybe applied to any of the context-user interfaces described herein simplyby including an application complication, allow the user to view updatedinformation from a particular application while also presenting a quickway to launch the corresponding application in the same user interfaceobject. Moreover, the application and/or application informationdepicted by the complication may further be customized using the editingmethods described in reference to FIG. 15 (see, e.g., screen 1560 and1570).

A user may navigate screens on, e.g., a portable multifunction device,that include many affordances. These affordances may represent, forexample, applications that may be launched on the device. One suchaffordance may activate a context-specific user interface, such as thosedescribed herein. In order to help the user recognize that a particularaffordance corresponds to launching a context-specific user interface,an animation that visually connects the affordance to the interface maybe desirable.

FIG. 18C shows an exemplary user interface for editing a clock face thatcontains more than one complication, such as the ones depicted in FIGS.18A and 18B. FIG. 18C again depicts device 1800 displaying screen 1802,which includes clock face 1804, affordance 1806 representing a weatherapplication, and affordance 1808 representing a calendar application.

As discussed above in reference to FIG. 15, a user may customize thecomplications displayed on screen 1802 by entering clock face edit mode.The user contacts the touch-sensitive display of device 1800 with touch1814. Touch 1814 has a characteristic intensity above an intensitythreshold, which prompts device 1800 to enter a clock face edit mode,shown on screen 1840. Device 1800 indicates that the user has enteredclock face edit mode by visually distinguishing the clock face. In thisexample, screen 1840 shows a smaller version of the display of screen1802 (e.g., 1842), which includes a reduced size clock face, reducedsize complication 1844, which is based on complication 1806, and reducedsize complication 1846, which is based on complication 1808.

A user selects this clock face for editing by contacting displayed clockface 1842 (e.g., touch 1850). In some embodiments, touch 1850 is acontact on the touch-sensitive display. In some embodiments, touch 1850is a contact on the touch-sensitive display with a characteristicintensity above an intensity threshold. This causes device 1800 to enterinto clock face edit mode and display screen 1860. Screen 1860 displaysclock face 1862 for editing. Currently, affordance 1864 representing theweather application is selected for editing, as highlighted by outline1866. Also displayed is positional indicator 1868, which indicates theposition of the displayed complication in a series of complicationoptions using line 1870. Positional indicator 1868 further indicates tothe user that a rotatable input mechanism may be used to cycle throughoptions available for editing affordance 1864 (e.g., which set ofinformation from the weather application to display, or anotherapplication from which a set of information may be displayed). Pagingaffordance 1872 also displays the position of the aspect of clock face1862 currently selected for editing (i.e., complication 1864) in aseries of editable aspects.

Screen 1860 also displays affordance 1874, which represents the calendarapplication. To select this complication for editing, the user contactsdisplayed affordance 1874 (e.g., touch 1876). In response, device 1800displays screen 1880. Like screen 1860, screen 1880 displays clock face1862, affordance 1864 (which represents the weather application),positional indicator 1868, and affordance 1874 (which represents theweather application). Affordance 1874 is now highlighted for editing, asshown by outline 1882. The position of this complication option isdepicted by line 1884 in positional indicator 1868. Finally, pagingaffordance 1886 has been updated to display the position of affordancecomplication 1874 in a series of editable aspects of clock face 1862.The user may now edit the set of information displayed by affordance1874 using the rotatable input mechanism (e.g., which set of informationfrom the calendar application to display, or another application fromwhich a set of information may be displayed). In summary, while in clockface edit mode, a user may select a complication for editing when morethan one complication is displayed by contacting the displayedcomplication. In some embodiments, this causes the affordance to behighlighted (e.g., by a visible outline or other means for visiblydistinguishing the affordance described herein).

FIG. 19 shows exemplary context-specific user interfaces that may beoperated on device 1900. Device 1900 may be device 100, 300, or 500 insome embodiments. In some embodiments, the electronic device has atouch-sensitive display (e.g., touchscreen 504).

Device 1900 displays user interface screen 1902, which includes aplurality of affordances (e.g., affordances 1904 and 1906). Affordance1906 represents a clock face that includes an indication of time (e.g.,the hour hand, minute hand, and tick marks) and an outline (e.g., acircle or a polygon such as a square with rounded corners). In someembodiments, the clock face may indicate the current time. The usercontacts the touch-sensitive display (e.g., touch 1908) at affordance1906, and in response, device 1900 displays, sequentially, screens 1910,1920, and 1930 in continuous on-screen animation.

Screen 1910 shows outline 1912 being animated by progressivelydisplaying the element in a rotational motion (e.g., as if it is beingfilled in or drawn in a clockwise manner). Next, screen 1920 shows fulloutline 1922 and hour hand and minute hand 1924. Finally, screen 1930shows full outline 1932, hour hand and minute hand 1934, and hourindication 1936. Like the outline, the hour indications may also beprogressively filled in sequentially (e.g., in a clockwise manner).Importantly, at least one of the elements from affordance 1906 ismaintained on screen 1930 (e.g., an outline, or the hour and minutehands), but at a larger display size.

While FIG. 19 depicts an analog clock face with an hour hand and aminute hand, the techniques described in reference to FIG. 19 may applyto many context-specific user interfaces. For example, if the userinterface displays a representation of the Earth (as shown in FIG. 8),the affordance in the plurality of affordances may depict an Earth, andthe outline of the Earth may be retained and/or drawn in using aclockwise motion.

A user may also wish to receive an indication from a portablemultifunction device that a missed or unread notification is available.Thus, in any of the embodiments described herein, a device may receive anotification, determine whether the notification has been missed (e.g.,not viewed or marked as not read), and in accordance with adetermination that the notification has been missed, display anaffordance indicating a missed notification. in accordance with adetermination that the notification has not been missed, the device mayforego displaying the affordance indicating a missed notification. Insome embodiments, an aspect of the displayed affordance represents anumber of missed notifications received by the electronic device. Forexample, the displayed affordance may change color, change size, or beanimated (e.g., to depict pulsing) to represent a number of missednotifications. In some embodiments, in response to receiving datarepresenting user viewing of the missed notification, the device mayremove the displayed affordance. This provides the user a quick visualreminder that a notification may be viewed.

A user may also wish to launch an application, such as a stopwatchapplication, from any of the context-specific user interfaces describedherein. Thus, in any of the embodiments described herein, a device maydisplay a stopwatch progress affordance that indicates a currentlyrunning stopwatch application. For example, the stopwatch progressaffordance may depict a representation of a digital stopwatch (e.g.,similar to affordance 1694 in FIG. 16C). This representation may becontinuously updated to indicate a stopwatch time generated by thecurrently running stopwatch application. A user may contact thestopwatch progress affordance, and in response to detecting the contact,the device may launch the stopwatch application. This provides afunctional reminder that a stopwatch is currently running from anycontext-specific user interface.

When traveling, a user may wish to quickly access the time at home, oranother designated location. Thus, in any of the embodiments describedherein, a device may include a location sensor (e.g., GPS sensor 532and/or GPS module 135). While any clock face is displayed on thedisplay, a user may contact the display, and in response to detectingthe contact, the device may access a designated home location (e.g., ahome time zone). The device may obtain a current time zone (i.e., at thecurrent location of the device), determine whether the current time zoneis different from the home time zone, and in accordance with adetermination that the current time zone is different from the home timezone, update the displayed clock face to indicate current time at thehome time zone. In accordance with a determination that the current timezone is not different from the home time zone, the device may continueto display the same clock face to indicate current time at both the hometime zone and the current time zone.

In some embodiments, a user may designate the home time zone. Forexample, the device may provide a user interface for designating thehome time zone.

In other embodiments, the device may designate the home time zone. Forexample, the device could base this designation on data representingamount of time spent at a location, which times of day are spent at thelocation, and/or a number of contact entries associated with thelocation. In this way, the device may automatically be able to designatea home time zone.

A user may wish to display different context-specific user interfaces,such as those described herein, depending on a particular context. Forexample, a user may wish to display a specific context-specific userinterface or specific content (e.g., information provided by a displayedcomplication) while at work, then display a different context-specificuser interface or different content while at home. In some embodiments,a user may designate a time of day to change the displayedcontext-specific user interface. In some embodiments, a user maydesignate an interval during the day wherein a particularcontext-specific user interface is displayed. In other embodiments, thedevice may include a location sensor, and a user may designate acontext-specific user interface to be displayed at a particular location(e.g., a home or office). In some embodiments, the device may employ aheuristic method to track previous user interactions, such as a time ofday and/or location whereupon a user has changed context-specific userinterfaces, a particular context-specific user interface that has beenselected or de-selected, and the like. For example, if a user haschanged context-specific user interfaces at an approximately regulartime after returning home from work, the device may display a promptasking if the user would like to change context-specific user interfacesat the same time on the following day. In some embodiments, the deviceautomatically changes the context-specific user interface based on aprevious user interaction. In other embodiments, the device prompts theuser to change the context-specific user interface based on a previoususer interaction.

It may be desirable to vary the display of any of the devices describedherein. Thus, in any of the embodiments described herein, a device maydisplay a clock face that includes a plurality of pixels, detect amovement of the device (as described above), and in response todetecting the movement, move the displayed clock face on the display.Moving may include modifying a subset of the pixels in the plurality(e.g., by changing color and/or intensity of one or more pixels).

A user may wish to use a virtual tachymeter (e.g., a tachymeter that isnot based on a physical tachymeter dial built onto the device) on any ofthe devices described herein. A virtual tachymeter may be provided, forexample, by a tachymeter user interface object that may be displayed ona dedicated tachymeter user interface screen, or on any of the userinterface screens described herein (e.g., as a tachymeter complication).The user may provide a user input to start the virtual tachymeter and,subsequently the user may stop the virtual tachymeter by providing asecond user input. For example, the tachymeter user interface object mayinclude a start affordance, a stop affordance, or a combined start/stopaffordance. The user may start the virtual tachymeter by contacting thestart affordance or the start/stop affordance and stop the virtualtachymeter by contacting the stop affordance or the start/stopaffordance. In another example, one or both user inputs may be an inputon a mechanical button (e.g., a rotation and/or depression of therotatable and depressible input mechanism 506, and/or a press on button508) to start and/or stop the virtual tachymeter. In some embodiments,one or both user inputs may be an audio (e.g., verbal) input.

After the user has stopped the virtual tachymeter, the device maydisplay a time value based on the time elapsed between start and stop.This time value may be based on, for example, a number of units of timein a predetermined interval (e.g., the number of seconds in an hour). Insome embodiments, the displayed time value may be based on the number ofunits of time in the predetermined interval (e.g., the number of secondsin an hour) divided by the time elapsed between start and stop. In someembodiments, the user may customize the units of time used by thetachymeter, the units of time in the predetermined interval, and/or thepredetermined interval. In some embodiments, while the virtualtachymeter is running, the tachymeter user interface object may includean updating display to indicate the passage of time, such as a runningor continuously updated countdown of the time value, a rotating shape,and the like. Advantageously, since the tachymeter is virtual, it maymeasure any increment or interval of time because it is not constrainedor fixed like a traditional tachymeter, such as a watch tachymeter. Forexample, a watch tachymeter is typically limited to measuring times lessthan or equal to 60 seconds, because the displayed time values are fixed(e.g., painted or etched onto a tachymeter dial) and only apply tovalues within one full rotation of the second hand.

A user may wish to use a virtual telemeter (e.g., a telemeter that isnot based on a physical telemeter dial built onto the device) on any ofthe devices described herein. A virtual telemeter may be provided, forexample, by a telemeter user interface object that may be displayed on adedicated telemeter user interface screen, or on any of the userinterface screens described herein (e.g., as a telemeter complication).

The user may provide a user input to start the virtual telemeter and,subsequently the user may stop the virtual telemeter by providing asecond user input. For example, the telemeter user interface object mayinclude a start affordance, a stop affordance, or a combined start/stopaffordance. The user may start the virtual telemeter by contacting thestart affordance or the start/stop affordance and stop the virtualtelemeter by contacting the stop affordance or the start/stopaffordance. In another example, one or both user inputs may be an inputon a mechanical button (e.g., a rotation and/or depression of therotatable and depressible input mechanism 506, and/or a press on button508) to start and/or stop the virtual telemeter. In some embodiments,one or both user inputs may be an audio (e.g., verbal) input. After theuser has stopped the virtual telemeter, the device may display adistance based on the time elapsed between start and stop. This distancemay be based on the speed of sound. For example, the user may seelightning, start the telemeter, and stop the telemeter when the userhears thunder. In this case, the distance reported by the telemeter willindicate the distance between the user and the lightning, based on thetime interval between when the light reaches the user and when the soundreaches the user. In some embodiments, the user may designate the unitsfor reporting the distance (e.g., kilometers, miles, etc.). In someembodiments, while the virtual telemeter is running, the telemeter userinterface object may include an updating display to indicate the passageof time, such as a running or continuously updated distance, a rotatingshape, and the like. Advantageously, since the telemeter is virtual, itmay measure any increment or interval of time because it is notconstrained or fixed like a traditional telemeter, such as a watchtelemeter. For example, a watch telemeter is typically limited tomeasuring times less than or equal to 60 seconds, because the displayedtime values are fixed (e.g., painted or etched onto a telemeter dial)and only apply to values within one full rotation of the second hand.

A user may wish to use a repeated interval timer on any of the devicesdescribed herein, e.g., a timer that provides a user alert that isrepeated at a certain interval. For example, if the user is exercising(e.g., interval training), they may wish to receive an alert every 30seconds to change their mode of exercise or take a break. In anotherexample, a user taking medication may wish to receive an alert to taketheir medication every hour, 4 hours, 6 hours, 12 hours, 24 hours, andso forth. Any suitable interval or duration of time may be used. In someembodiments, the device may display a repeated interval timer userinterface. The repeated interval timer user interface may include, forexample, an affordance for the user to designate the interval, thetimescale for the interval (e.g., seconds, minutes, hours, days, weeks,months, years, etc.), and the like. In response to receiving datarepresenting a user-designated time interval, the device may provide auser alert that is repeated at times based on the user-designated timeinterval. In some embodiments, the alert may include a visual alert, anaudio alert, and/or a haptic alert (e.g., using haptic feedback module133 and tactile output generator 167), or any combination thereof.Rather than being based on a designated end point (e.g., a reminder fora particular day or time), the repeated interval timer is based onproviding the user a demarcation of a particular interval of time. Insome embodiments, the repeated interval timer runs until the user endsthe timer. In some embodiments, the device may further display anaffordance for ending the repeated interval timer (e.g., as part of therepeated interval timer user interface, or at the time of the useralert).

In some embodiments, any of the devices described herein may furthergenerate or receive a user alert including information and display auser notification based on the alert on any of the user interfacescreens described herein. The user notification may be, for example, anotification banner displayed across a portion of the display. Thenotification banner may include a portion of the information of thealert. An example of a user alert may include without limitation adetermination that the user has crossed the boundary of a time zone. Insome embodiments, the device has a location sensor (e.g., GPS sensor 532and/or GPS module 135), and the device obtains a current location of thedevice from the location sensor. Using the location sensor, the devicemay determine whether the current location of the device is in adifferent time zone, as compared to a previous location of the device,for example the location of the device at the time of a previous userinteraction (e.g., the last time the user looked at the display, or thelast time the device detected a user movement of the device, such as awrist raise). In accordance with the determination that the currentlocation is in a different time zone than the previous location, thedevice may display a notification banner across a portion of thedisplay. In some embodiments, the notification banner may include analert indicating that the user has crossed a time zone, a notificationof the current time in the new time zone, and so forth. In someembodiments, the device may prompt the user whether to accept the timechange (e.g., the device may display an affordance for accepting thetime change and/or an affordance for rejecting the time change). Theuser prompt may be displayed as part of the notification banner, or theuser prompt may be displayed in response to detecting a user contact onthe displayed notification banner. In response to receiving dataindicating a user acceptance of the time change (e.g., a contact on thedisplayed affordance for accepting the time change), the device mayupdate the displayed time based on the new time zone. In response toreceiving data indicating a user rejection of the time change (e.g., acontact on the displayed affordance for rejecting the time change), thedevice may forego updating the displayed time based on the new timezone.

FIG. 20 is a flow diagram illustrating process 2000 for providingcontext-specific user interfaces. In some embodiments, process 2000 maybe performed at an electronic device with a touch-sensitive display,such as device 100 (FIG. 1A), 300 (FIG. 3), 500 (FIG. 5) or 600 (FIGS.6A and 6B). Some operations in process 2000 may be combined, the orderof some operations may be changed, and some operations may be omitted.Process 2000 provides context-specific user interfaces that give theuser an immediate indication of elapsed time before viewing, makingthese interfaces less confusing and, thus, conserving power andincreasing battery life.

At block 2002, the device receives data representing a user input (e.g.,602). At block 2004, responsive at least in part to receiving the data,the device displays a user interface screen including a clock face(e.g., 606) indicating a first time (the first time precedes a currenttime). At block 2006, the device updates the user interface screen byanimating the clock face to transition from indicating the first time toindicating the current time (animation represents the passage of timefrom the first time to the current time; see, e.g., 612).

Note that details of the processes described above with respect toprocess 2000 (FIG. 20) are also applicable in an analogous manner to themethods described below. For example, process 2100 (FIG. 21), process2200 (FIG. 22), process 2300 (FIG. 23), process 2400 (FIG. 24), process2500 (FIG. 25), process 2600 (FIG. 26), process 2700 (FIG. 27A), process2710 (FIG. 27B), process 2720 (FIG. 27C), process 2730 (FIG. 27D),process 2740 (FIG. 27E), process 2750 (FIG. 27F), process 2800 (FIG.28), process 2900 (FIG. 29), process 3000 (FIG. 30), process 3100 (FIG.31), process 3200 (FIG. 32), and/or process 3300 (FIG. 33) may includeone or more of the characteristics of the various methods describedabove with reference to process 2000. For brevity, these details are notrepeated below.

It should be understood that the particular order in which theoperations in FIG. 20 have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of process2100 (FIG. 21), process 2200 (FIG. 22), process 2300 (FIG. 23), process2400 (FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26), process2700 (FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C),process 2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG.27F), process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG.30), process 3100 (FIG. 31), process 3200 (FIG. 32), and process 3300(FIG. 33) may be incorporated with one another. Thus, the techniquesdescribed with respect to process 2000 may be relevant to process 2100(FIG. 21), process 2200 (FIG. 22), process 2300 (FIG. 23), process 2400(FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26), process 2700(FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C), process2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG. 27F),process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG. 30),process 3100 (FIG. 31), process 3200 (FIG. 32), and/or process 3300(FIG. 33).

FIG. 21 is a flow diagram illustrating process 2100 for providingcontext-specific user interfaces. In some embodiments, process 2100 maybe performed at an electronic device with a touch-sensitive display,such as device 100 (FIG. 1A), 300 (FIG. 3), 500 (FIG. 5) or 700 (FIGS.7A and 7B). Some operations in process 2100 may be combined, the orderof some operations may be changed, and some operations may be omitted.Process 2100 provides context-specific user interfaces that combine astopwatch function and a timekeeping function, making these interfacesat once multifunctional and less confusing to the user, thus conservingpower and increasing battery life.

At block 2102, the device displays a clock face that indicates currenttime and includes a user interface object with an hour hand and a minutehand, one or more indications of an hourly timescale, and a stopwatchhand (e.g., as on screen 702). At block 2104, the device receives datarepresenting a user input (e.g., touch 712). At block 2106, responsiveat least in part to receiving the data, the device substitutes the oneor more indications of an hourly timescale with an indication of a firsttimescale for the stopwatch hand (e.g., 724). At block 2108, the deviceanimates the stopwatch hand to reflect passage of time (e.g., cf. 726and 736).

Note that details of the processes described above with respect toprocess 2100 (FIG. 21) are also applicable in an analogous manner to themethods described below. For example, process 2000 (FIG. 20), process2200 (FIG. 22), process 2300 (FIG. 23), process 2400 (FIG. 24), process2500 (FIG. 25), process 2600 (FIG. 26), process 2700 (FIG. 27A), process2710 (FIG. 27B), process 2720 (FIG. 27C), process 2730 (FIG. 27D),process 2740 (FIG. 27E), process 2750 (FIG. 27F), process 2800 (FIG.28), process 2900 (FIG. 29), process 3000 (FIG. 30), process 3100 (FIG.31), process 3200 (FIG. 32), and/or process 3300 (FIG. 33) may includeone or more of the characteristics of the various methods describedabove with reference to process 2100. For brevity, these details are notrepeated below.

It should be understood that the particular order in which theoperations in FIG. 21 have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of process2000 (FIG. 20), process 2200 (FIG. 22), process 2300 (FIG. 23), process2400 (FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26), process2700 (FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C),process 2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG.27F), process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG.30), process 3100 (FIG. 31), process 3200 (FIG. 32), and process 3300(FIG. 33) may be incorporated with one another. Thus, the techniquesdescribed with respect to process 2100 may be relevant to process 2000(FIG. 20), process 2200 (FIG. 22), process 2300 (FIG. 23), process 2400(FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26), process 2700(FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C), process2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG. 27F),process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG. 30),process 3100 (FIG. 31), process 3200 (FIG. 32), and/or process 3300(FIG. 33).

FIG. 22 is a flow diagram illustrating process 2200 for providingcontext-specific user interfaces. In some embodiments, process 2200 maybe performed at an electronic device with a touch-sensitive display,such as device 100 (FIG. 1A), 300 (FIG. 3), 500 (FIG. 5), 800 (FIG. 8),900 (FIG. 9), or 1000 (FIG. 10). Some operations in process 2200 may becombined, the order of some operations may be changed, and someoperations may be omitted. Process 2200 provides context-specific userinterfaces that provide timekeeping and geographical/astronomicalinformation, making these interfaces at once multifunctional and lessconfusing to the user, thus conserving power and increasing batterylife.

At block 2202, the device displays a user interface screen that includesa first affordance representing a simulation of a first region of theEarth as illuminated by the Sun at current time (e.g., 804) and a secondaffordance that indicates the current time (e.g., 806). At block 2204,the device receives data representing a user input (e.g., swipe 812). Atblock 2206, responsive at least in part to receiving the data, thedevice rotates the simulation of the Earth to display a second region ofthe Earth as illuminated by the Sun at the current time (e.g., 822).Optionally, at block 2206, the device displays a third affordancerepresenting a moon (e.g., 808, 826, 846, 1016, and 1034), detects acontact on the displayed third affordance, and responsive at least inpart to detecting the contact, updates the user interface screen bydisplaying a fourth affordance representing a simulation of the Moon asseen from the Earth at the current time (e.g., 904) and a fifthaffordance that indicates the current time (e.g., 906). Optionally, atblock 2206, the device displays a sixth affordance representing a solarsystem (e.g., 810, 828, and 848), detects a contact on the displayedsixth affordance, and responsive at least in part to detecting thecontact, updates the user interface screen by displaying a seventhaffordance including representations of the Sun, the Earth, and one ormore non-Earth planets at their respective positions at a current time(e.g., 1004) and an eighth affordance that indicates the current time(e.g., 1012).

Note that details of the processes described above with respect toprocess 2200 (FIG. 22) are also applicable in an analogous manner to themethods described below. For example, process 2000 (FIG. 20), process2100 (FIG. 21), process 2300 (FIG. 23), process 2400 (FIG. 24), process2500 (FIG. 25), process 2600 (FIG. 26), process 2700 (FIG. 27A), process2710 (FIG. 27B), process 2720 (FIG. 27C), process 2730 (FIG. 27D),process 2740 (FIG. 27E), process 2750 (FIG. 27F), process 2800 (FIG.28), process 2900 (FIG. 29), process 3000 (FIG. 30), process 3100 (FIG.31), process 3200 (FIG. 32), and/or process 3300 (FIG. 33) may includeone or more of the characteristics of the various methods describedabove with reference to process 2200. For brevity, these details are notrepeated below.

It should be understood that the particular order in which theoperations in FIG. 22 have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of process2000 (FIG. 20), process 2100 (FIG. 21), process 2300 (FIG. 23), process2400 (FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26), process2700 (FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C),process 2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG.27F), process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG.30), process 3100 (FIG. 31), process 3200 (FIG. 32), and process 3300(FIG. 33) may be incorporated with one another. Thus, the techniquesdescribed with respect to process 2200 may be relevant to process 2000(FIG. 20), process 2100 (FIG. 21), process 2300 (FIG. 23), process 2400(FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26), process 2700(FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C), process2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG. 27F),process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG. 30),process 3100 (FIG. 31), process 3200 (FIG. 32), and/or process 3300(FIG. 33).

FIG. 23 is a flow diagram illustrating process 2300 for providingcontext-specific user interfaces. In some embodiments, process 2300 maybe performed at an electronic device with a touch-sensitive display,such as device 100 (FIG. 1A), 300 (FIG. 3), 500 (FIG. 5) or 1100 (FIGS.11A-C). Some operations in process 2300 may be combined, the order ofsome operations may be changed, and some operations may be omitted.Process 2300 provides context-specific user interfaces that allow theuser to view current time of day with respect to daylight/nighttimeconditions, making these interfaces at once multifunctional and lessconfusing to the user, thus conserving power and increasing batterylife.

At block 2302, the device displays a user interface screen that includesa first portion indicating daytime (e.g., 1104); a second portionindicating nighttime (e.g., 1106); a user interface object representinga sinusoidal wave with a period representing a day (e.g., 1108); a firstaffordance representing the Sun displayed at a first position on thesinusoidal wave indicating a current time of the day and whether thecurrent time of the day is during daytime or nighttime (e.g., 1110); anda second affordance, the second affordance indicating the current timeof day (e.g., 1114). Optionally, at block 2304, the device receives acontact on the touch-sensitive display at the first affordance at thefirst position indicating the current time (e.g., 1148). Optionally, atblock 2306, while continuing to receive the user contact, the devicedetects movement of the user contact from the first position to a secondposition on the displayed sinusoidal wave without a break in contact ofthe user contact on the touch-sensitive display (second position on thesinusoidal wave indicates a non-current time; see, e.g., touch 1166).Optionally, at block 2308, responsive at least in part to detecting thecontact at the second position, the device translates the firstaffordance on-screen from the first position on the sinusoidal wave tothe second position on the sinusoidal wave (translation tracks thedisplayed sinusoidal wave; see, e.g., 1162). Optionally, at block 2310,the device updates the second affordance to indicate the non-currenttime (e.g., 1168).

Note that details of the processes described above with respect toprocess 2300 (FIG. 23) are also applicable in an analogous manner to themethods described below. For example, process 2000 (FIG. 20), process2100 (FIG. 21), process 2200 (FIG. 22), process 2400 (FIG. 24), process2500 (FIG. 25), process 2600 (FIG. 26), process 2700 (FIG. 27A), process2710 (FIG. 27B), process 2720 (FIG. 27C), process 2730 (FIG. 27D),process 2740 (FIG. 27E), process 2750 (FIG. 27F), process 2800 (FIG.28), process 2900 (FIG. 29), process 3000 (FIG. 30), process 3100 (FIG.31), process 3200 (FIG. 32), and/or process 3300 (FIG. 33) may includeone or more of the characteristics of the various methods describedabove with reference to process 2300. For brevity, these details are notrepeated below.

It should be understood that the particular order in which theoperations in FIG. 23 have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of process2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process2400 (FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26), process2700 (FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C),process 2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG.27F), process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG.30), process 3100 (FIG. 31), process 3200 (FIG. 32), and process 3300(FIG. 33) may be incorporated with one another. Thus, the techniquesdescribed with respect to process 2300 may be relevant to process 2000(FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process 2400(FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26), process 2700(FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C), process2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG. 27F),process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG. 30),process 3100 (FIG. 31), process 3200 (FIG. 32), and/or process 3300(FIG. 33).

FIG. 24 is a flow diagram illustrating process 2400 for providingcontext-specific user interfaces. In some embodiments, process 2400 maybe performed at an electronic device with a touch-sensitive display,such as device 100 (FIG. 1A), 300 (FIG. 3), 500 (FIG. 5) or 1200 (FIG.12). Some operations in process 2400 may be combined, the order of someoperations may be changed, and some operations may be omitted. Process2400 provides context-specific user interfaces that provide an easilydistinguishable background image and indications of date and/or timecreated out of the background, making these interfaces easier for theuser to view, thus conserving power and increasing battery life.

At block 2402, the device displays a user interface screen that includesa background, based on an image (e.g., 1204 and 1212), with a pluralityof pixels (a subset of the pixels are modified in appearance relative tothe image such that the subset of pixels represents one or more of afirst user interface object indicating a date and a second userinterface object indicating a time of day; see, e.g., 1206 and/or 1208).Optionally, at block 2402, one of the first user interface object andthe second user interface object is a color independent of thebackground. Optionally, at block 2404, if one of the first userinterface object and the second user interface object is a colorindependent of the background, the device receives data representing abackground color of the background at a position of the displayed firstuser interface object or the displayed second user interface object(first color is different from background color at the position of thedisplayed first user interface object or the displayed second userinterface object).

Note that details of the processes described above with respect toprocess 2400 (FIG. 24) are also applicable in an analogous manner to themethods described below. For example, process 2000 (FIG. 20), process2100 (FIG. 21), process 2200 (FIG. 22), process 2300 (FIG. 23), process2500 (FIG. 25), process 2600 (FIG. 26), process 2700 (FIG. 27A), process2710 (FIG. 27B), process 2720 (FIG. 27C), process 2730 (FIG. 27D),process 2740 (FIG. 27E), process 2750 (FIG. 27F), process 2800 (FIG.28), process 2900 (FIG. 29), process 3000 (FIG. 30), process 3100 (FIG.31), process 3200 (FIG. 32), and/or process 3300 (FIG. 33) may includeone or more of the characteristics of the various methods describedabove with reference to process 2400. For brevity, these details are notrepeated below.

It should be understood that the particular order in which theoperations in FIG. 24 have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of process2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process2300 (FIG. 23), process 2500 (FIG. 25), process 2600 (FIG. 26), process2700 (FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C),process 2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG.27F), process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG.30), process 3100 (FIG. 31), process 3200 (FIG. 32), and process 3300(FIG. 33) may be incorporated with one another. Thus, the techniquesdescribed with respect to process 2400 may be relevant to process 2000(FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process 2300(FIG. 23), process 2500 (FIG. 25), process 2600 (FIG. 26), process 2700(FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C), process2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG. 27F),process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG. 30),process 3100 (FIG. 31), process 3200 (FIG. 32), and/or process 3300(FIG. 33).

FIG. 25 is a flow diagram illustrating process 2500 for providingcontext-specific user interfaces. In some embodiments, process 2500 maybe performed at an electronic device with a touch-sensitive display,such as device 100 (FIG. 1A), 300 (FIG. 3), 500 (FIG. 5) or 1200 (FIG.12). Some operations in process 2500 may be combined, the order of someoperations may be changed, and some operations may be omitted. Process2500 provides context-specific user interfaces that provide an easilydistinguishable background image and indications of date and/or timecreated out of the background, making these interfaces easier for theuser to view, thus conserving power and increasing battery life.

At block 2502, the device accesses a folder with two or more images. Atblock 2504, the device selects a first image from the folder. At block2506, the device displays a user interface screen (e.g., 1202) thatincludes a background based on the first image, the backgroundcontaining a plurality of pixels (a subset of the pixels are modified inappearance relative to the image such that the subset of pixelsrepresents one or more of a first user interface object indicating adate and second user interface object indicating a time of day; see,e.g., 1204). Optionally, at block 2508, after displaying the first userinterface screen, the device receives first data representing a userinput. Optionally, at block 2510, responsive at least in part toreceiving the first data, the device receives second data representingthe displayed first background. Optionally, at block 2512, the deviceselects a second image from the folder (second image is different fromthe first image; see, e.g., 1212). Optionally, at block 2514, the devicedisplays a second user interface screen (e.g., 1210) that includes abackground based on the first image, the background containing aplurality of pixels (a subset of the pixels are modified in appearancerelative to the image such that the subset of pixels represents one ormore of a first user interface object indicating a date and second userinterface object indicating a time of day.

Note that details of the processes described above with respect toprocess 2500 (FIG. 25) are also applicable in an analogous manner to themethods described below. For example, process 2000 (FIG. 20), process2100 (FIG. 21), process 2200 (FIG. 22), process 2300 (FIG. 23), process2400 (FIG. 24), process 2600 (FIG. 26), process 2700 (FIG. 27A), process2710 (FIG. 27B), process 2720 (FIG. 27C), process 2730 (FIG. 27D),process 2740 (FIG. 27E), process 2750 (FIG. 27F), process 2800 (FIG.28), process 2900 (FIG. 29), process 3000 (FIG. 30), process 3100 (FIG.31), process 3200 (FIG. 32), and/or process 3300 (FIG. 33) may includeone or more of the characteristics of the various methods describedabove with reference to process 2500. For brevity, these details are notrepeated below.

It should be understood that the particular order in which theoperations in FIG. 25 have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of process2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process2300 (FIG. 23), process 2400 (FIG. 24), process 2600 (FIG. 26), process2700 (FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C),process 2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG.27F), process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG.30), process 3100 (FIG. 31), process 3200 (FIG. 32), and process 3300(FIG. 33) may be incorporated with one another. Thus, the techniquesdescribed with respect to process 2500 may be relevant to process 2000(FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process 2300(FIG. 23), process 2400 (FIG. 24), process 2600 (FIG. 26), process 2700(FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C), process2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG. 27F),process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG. 30),process 3100 (FIG. 31), process 3200 (FIG. 32), and/or process 3300(FIG. 33).

FIG. 26 is a flow diagram illustrating process 2600 for providingcontext-specific user interfaces. In some embodiments, process 2600 maybe performed at an electronic device with a touch-sensitive display,such as device 100 (FIG. 1A), 300 (FIG. 3), 500 (FIG. 5) or 1300 (FIGS.13A and 13B). Some operations in process 2600 may be combined, the orderof some operations may be changed, and some operations may be omitted.Process 2600 provides context-specific user interfaces that providetimekeeping and a variable animated sequence, making these interfacesmore interactive and engaging to the user, thus improving the interfacewhile conserving power and increasing battery life.

At block 2602, the device detects a user input at a first time (e.g.,1304). At block 2604, responsive at least in part to detecting the userinput, the device displays a user interface screen including a firstuser interface object indicating the first time (e.g., 1306) and asecond user interface object (e.g., 1308). At block 2606, the deviceanimates the second user interface object with a sequential display of afirst animated sequence, a second animated sequence after the firstanimated sequence, and a third animated sequence after the secondanimated sequence (first animated sequence, second animated sequence,and third animated sequences are different; see, e.g., screens 1302,1310, and 1320). At block 2608, the device detects a second user inputat a second time of day (e.g., 1332). At block 2610, responsive at leastin part to detecting the second user input, the device accesses datarepresenting the previously displayed second animated sequence. At block2612, the device selects a fourth animated sequence different from thefirst animated sequence and the second animated sequence. At block 2614,the device displays a second user interface screen including the firstuser interface object (first user interface object indicates second timeof day; see, e.g., 1334) and a third user interface object related tothe second user interface object (e.g., 1336). At block 2616, the deviceanimates the third user interface object with a sequential display ofthe first animated sequence, the fourth animated sequence after thefirst animated sequence, and the third animated sequence after thefourth animated sequence (see, e.g., screens 1330, 1340, and 1350).

Note that details of the processes described above with respect toprocess 2600 (FIG. 26) are also applicable in an analogous manner to themethods described below. For example, process 2000 (FIG. 20), process2100 (FIG. 21), process 2200 (FIG. 22), process 2300 (FIG. 23), process2400 (FIG. 24), process 2500 (FIG. 25), process 2700 (FIG. 27A), process2710 (FIG. 27B), process 2720 (FIG. 27C), process 2730 (FIG. 27D),process 2740 (FIG. 27E), process 2750 (FIG. 27F), process 2800 (FIG.28), process 2900 (FIG. 29), process 3000 (FIG. 30), process 3100 (FIG.31), process 3200 (FIG. 32), and/or process 3300 (FIG. 33) may includeone or more of the characteristics of the various methods describedabove with reference to process 2600. For brevity, these details are notrepeated below.

It should be understood that the particular order in which theoperations in FIG. 26 have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of process2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process2300 (FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process2700 (FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C),process 2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG.27F), process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG.30), process 3100 (FIG. 31), process 3200 (FIG. 32), and process 3300(FIG. 33) may be incorporated with one another. Thus, the techniquesdescribed with respect to process 2600 may be relevant to process 2000(FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process 2300(FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process 2700(FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C), process2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG. 27F),process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG. 30),process 3100 (FIG. 31), process 3200 (FIG. 32), and/or process 3300(FIG. 33).

FIG. 27A is a flow diagram illustrating process 2700 for providingcontext-specific user interfaces. In some embodiments, process 2700 maybe performed at an electronic device with a touch-sensitive display,such as device 100 (FIG. 1A), 300 (FIG. 3), 500 (FIG. 5) or 1400 (FIG.14A). Some operations in process 2700 may be combined, the order of someoperations may be changed, and some operations may be omitted. Process2700 provides context-specific user interfaces that are less confusingto the user, thus conserving power and increasing battery life.

At block 2702, the device detects a user movement of the device (e.g.,1404). At block 2704, responsive at least in part to detecting themovement, the device displays an animated reveal of a clock face bydisplaying an hour hand and a minute hand (e.g., 1424), displaying afirst hour indication (e.g., 1436), and displaying a second hourindication after the first (second hour indication is after the firsthour indication on clock face in clockwise direction; see, e.g., 1438).

Note that details of the processes described above with respect toprocess 2700 (FIG. 27A) are also applicable in an analogous manner tothe methods described below. For example, process 2000 (FIG. 20),process 2100 (FIG. 21), process 2200 (FIG. 22), process 2300 (FIG. 23),process 2400 (FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26),process 2710 (FIG. 27B), process 2720 (FIG. 27C), process 2730 (FIG.27D), process 2740 (FIG. 27E), process 2750 (FIG. 27F), process 2800(FIG. 28), process 2900 (FIG. 29), process 3000 (FIG. 30), process 3100(FIG. 31), process 3200 (FIG. 32), and/or process 3300 (FIG. 33) mayinclude one or more of the characteristics of the various methodsdescribed above with reference to process 2700. For brevity, thesedetails are not repeated below.

It should be understood that the particular order in which theoperations in FIG. 27A have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of process2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process2300 (FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process2600 (FIG. 26), process 2710 (FIG. 27B), process 2720 (FIG. 27C),process 2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG.27F), process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG.30), process 3100 (FIG. 31), process 3200 (FIG. 32), and process 3300(FIG. 33) may be incorporated with one another. Thus, the techniquesdescribed with respect to process 2700 may be relevant to process 2000(FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process 2300(FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process 2600(FIG. 26), process process 2710 (FIG. 27B), process 2720 (FIG. 27C),process 2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG.27F), process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG.30), process 3100 (FIG. 31), process 3200 (FIG. 32), and/or process 3300(FIG. 33).

FIG. 27B is a flow diagram illustrating process 2710 for indicating timeusing a character-based user interface. In some embodiments, process2710 may be performed at an electronic device with a display and atouch-sensitive surface, such as device 100 (FIG. 1), 300 (FIG. 3), 500(FIG. 5), and/or 14000 (FIGS. 14B-T). Some operations in process 2710may be combined, the order of some operations may be changed, and someoperations may be omitted. Process 2710 provides character-based userinterfaces that are less confusing, more interactive, and more engagingto the user, thus improving the interface while conserving power andincreasing battery life.

At block 2712, a character user interface object that indicates a firsttime is displayed. The character user interface object includesrepresentations of a first limb and a second limb and indicates a firsttime by indicating a first hour with the first limb and a first minutewith the second limb. At block 2714, the character user interface objectis updated to indicate a second time by indicating a second hour withthe first limb and a second minute with the second limb. Optionally, atblock 2714, updating the character user interface object to indicate asecond time includes an extension of the first limb and a retraction ofthe second limb.

Note that details of the processes described above with respect toprocess 2710 (FIG. 27B) are also applicable in an analogous manner tothe methods described below. For example, process 2000 (FIG. 20),process 2100 (FIG. 21), process 2200 (FIG. 22), process 2300 (FIG. 23),process 2400 (FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26),process 2700 (FIG. 27A), process 2720 (FIG. 27C), process 2730 (FIG.27D), process 2740 (FIG. 27E), process 2750 (FIG. 27F), process 2800(FIG. 28), process 2900 (FIG. 29), process 3000 (FIG. 30), process 3100(FIG. 31), process 3200 (FIG. 32), and/or process 3300 (FIG. 33) mayinclude one or more of the characteristics of the various methodsdescribed above with reference to process 2710. For brevity, thesedetails are not repeated below.

It should be understood that the particular order in which theoperations in FIG. 27B have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of process2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process2300 (FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process2600 (FIG. 26), process 2700 (FIG. 27A), process 2720 (FIG. 27C),process 2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG.27F), process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG.30), process 3100 (FIG. 31), process 3200 (FIG. 32), and process 3300(FIG. 33) may be incorporated with one another. Thus, the techniquesdescribed with respect to process 2710 may be relevant to process 2000(FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process 2300(FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process 2600(FIG. 26), process 2700 (FIG. 27A), process 2720 (FIG. 27C), process2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG. 27F),process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG. 30),process 3100 (FIG. 31), process 3200 (FIG. 32), and/or process 3300(FIG. 33).

FIG. 27C is a flow diagram illustrating process 2720 for indicating timeusing a character-based user interface. In some embodiments, process2720 may be performed at an electronic device with a display and atouch-sensitive surface, such as device 100 (FIG. 1), 300 (FIG. 3), 500(FIG. 5), and/or 14000 (FIGS. 14B-T). Some operations in process 2720may be combined, the order of some operations may be changed, and someoperations may be omitted. Process 2720 provides character-based userinterfaces that are less confusing, more interactive, and more engagingto the user, thus improving the interface while conserving power andincreasing battery life.

At block 2722, a character user interface object that indicates a firsttime value is displayed. The character user interface object includes arepresentation of a first limb with a first endpoint and a secondendpoint. The first endpoint is an axis of rotation for the limb, andthe second endpoint indicates a first time value. At block 2724, thecharacter user interface object is updated to indicate a second timevalue. Updating the character user interface object includes moving thefirst endpoint and moving the second endpoint to indicate the secondtime value.

Note that details of the processes described above with respect toprocess 2720 (FIG. 27C) are also applicable in an analogous manner tothe methods described below. For example, process 2000 (FIG. 20),process 2100 (FIG. 21), process 2200 (FIG. 22), process 2300 (FIG. 23),process 2400 (FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26),process 2700 (FIG. 27A), process 2710 (FIG. 27B), process 2730 (FIG.27D), process 2740 (FIG. 27E), process 2750 (FIG. 27F), process 2800(FIG. 28), process 2900 (FIG. 29), process 3000 (FIG. 30), process 3100(FIG. 31), process 3200 (FIG. 32), and/or process 3300 (FIG. 33) mayinclude one or more of the characteristics of the various methodsdescribed above with reference to process 2720. For brevity, thesedetails are not repeated below.

It should be understood that the particular order in which theoperations in FIG. 27C have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of process2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process2300 (FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process2600 (FIG. 26), process 2700 (FIG. 27A), process 2710 (FIG. 27B),process 2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG.27F), process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG.30), process 3100 (FIG. 31), process 3200 (FIG. 32), and process 3300(FIG. 33) may be incorporated with one another. Thus, the techniquesdescribed with respect to process 2720 may be relevant to process 2000(FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process 2300(FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process 2600(FIG. 26), process 2700 (FIG. 27A), process 2710 (FIG. 27B), process2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG. 27F),process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG. 30),process 3100 (FIG. 31), process 3200 (FIG. 32), and/or process 3300(FIG. 33).

FIG. 27D is a flow diagram illustrating process 2730 for indicating timeusing a character-based user interface. In some embodiments, process2730 may be performed at an electronic device with a display and atouch-sensitive surface, such as device 100 (FIG. 1), 300 (FIG. 3), 500(FIG. 5), and/or 14000 (FIGS. 14B-T). Some operations in process 2730may be combined, the order of some operations may be changed, and someoperations may be omitted. Process 2730 provides character-based userinterfaces that are less confusing, more interactive, and more engagingto the user, thus improving the interface while conserving power andincreasing battery life.

At block 2732, a character user interface object that indicates a firsttime value is displayed. The character user interface object includes arepresentation of a first limb with a first segment and a secondsegment. The first segment of the limb connects a first endpoint to ajoint. The second segment connects a second endpoint to the joint. Thejoint is an axis of rotation for the second segment. The position of thesecond endpoint indicates a first time value. At block 2734, thecharacter user interface object is updated to indicate a second timevalue. Updating the character user interface object includes moving thesecond endpoint along the axis of rotation to indicate the second timevalue.

Note that details of the processes described above with respect toprocess 2730 (FIG. 27D) are also applicable in an analogous manner tothe methods described below. For example, process 2000 (FIG. 20),process 2100 (FIG. 21), process 2200 (FIG. 22), process 2300 (FIG. 23),process 2400 (FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26),process 2700 (FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG.27C), process 2740 (FIG. 27E), process 2750 (FIG. 27F), process 2800(FIG. 28), process 2900 (FIG. 29), process 3000 (FIG. 30), process 3100(FIG. 31), process 3200 (FIG. 32), and/or process 3300 (FIG. 33) mayinclude one or more of the characteristics of the various methodsdescribed above with reference to process 2730. For brevity, thesedetails are not repeated below.

It should be understood that the particular order in which theoperations in FIG. 27D have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of process2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process2300 (FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process2600 (FIG. 26), process 2800 (FIG. 28), process 2900 (FIG. 29), process3000 (FIG. 30), process 3100 (FIG. 31), process 3200 (FIG. 32), andprocess 3300 (FIG. 33) may be incorporated with one another. Thus, thetechniques described with respect to process 2730 may be relevant toprocess 2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22),process 2300 (FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25),process 2600 (FIG. 26), process 2700 (FIG. 27A), process 2710 (FIG.27B), process 2720 (FIG. 27C), process 2740 (FIG. 27E), process 2750(FIG. 27F), process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000(FIG. 30), process 3100 (FIG. 31), process 3200 (FIG. 32), and/orprocess 3300 (FIG. 33).

FIG. 27E is a flow diagram illustrating process 2740 for indicating timeusing a character-based user interface. In some embodiments, process2740 may be performed at an electronic device with a display and atouch-sensitive surface, such as device 100 (FIG. 1), 300 (FIG. 3), 500(FIG. 5), and/or 14000 (FIGS. 14B-T). Some operations in process 2740may be combined, the order of some operations may be changed, and someoperations may be omitted. Process 2740 provides character-based userinterfaces that are less confusing, more interactive, and more engagingto the user, thus improving the interface while conserving power andincreasing battery life.

At block 2742, a character user interface object that indicates time isdisplayed. At block 2744, first data indicative of an event is received.At block 2746, a determination is made as to whether the event meets acondition. At block 2748, in accordance with the determination that theevent meets the condition, the character user interface object isupdated by changing a visual aspect of the character user interfaceobject.

Note that details of the processes described above with respect toprocess 2740 (FIG. 27E) are also applicable in an analogous manner tothe methods described below. For example, process 2000 (FIG. 20),process 2100 (FIG. 21), process 2200 (FIG. 22), process 2300 (FIG. 23),process 2400 (FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26),process 2700 (FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG.27C), process 2730 (FIG. 27D), process 2750 (FIG. 27F), process 2800(FIG. 28), process 2900 (FIG. 29), process 3000 (FIG. 30), process 3100(FIG. 31), process 3200 (FIG. 32), and/or process 3300 (FIG. 33) mayinclude one or more of the characteristics of the various methodsdescribed above with reference to process 2740. For brevity, thesedetails are not repeated below.

It should be understood that the particular order in which theoperations in FIG. 27E have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of process2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process2300 (FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process2600 (FIG. 26), process 2700 (FIG. 27A), process 2710 (FIG. 27B),process 2720 (FIG. 27C), process 2730 (FIG. 27D), process 2750 (FIG.27F), process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG.30), process 3100 (FIG. 31), process 3200 (FIG. 32), and process 3300(FIG. 33) may be incorporated with one another. Thus, the techniquesdescribed with respect to process 2740 may be relevant to process 2000(FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process 2300(FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process 2600(FIG. 26), process 2700 (FIG. 27A), process 2710 (FIG. 27B), process2720 (FIG. 27C), process 2730 (FIG. 27D), process 2750 (FIG. 27F),process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG. 30),process 3100 (FIG. 31), process 3200 (FIG. 32), and/or process 3300(FIG. 33).

FIG. 27F is a flow diagram illustrating process 2750 for indicating timeusing a character-based user interface. In some embodiments, process2750 may be performed at an electronic device with a display and atouch-sensitive surface, such as device 100 (FIG. 1), 300 (FIG. 3), 500(FIG. 5), and/or 14000 (FIGS. 14B-T). Some operations in process 2750may be combined, the order of some operations may be changed, and someoperations may be omitted. Process 2750 provides character-based userinterfaces that are less confusing, more interactive, and more engagingto the user, thus improving the interface while conserving power andincreasing battery life.

At block 2752, the display is set to an inactive state. At block 2754,first data indicative of an event is received. At block 2756, inresponse to receiving the first data, the display is set to an activestate. At block 2758, a character user interface object is displayed ona side of the display. At block 2760, the character user interfaceobject is animated towards a center of the display. At block 2762, thecharacter user interface object is displayed at the center of thedisplay in a position that indicates a current time.

Note that details of the processes described above with respect toprocess 2750 (FIG. 27F) are also applicable in an analogous manner tothe methods described below. For example, process 2000 (FIG. 20),process 2100 (FIG. 21), process 2200 (FIG. 22), process 2300 (FIG. 23),process 2400 (FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26),process 2700 (FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG.27C), process 2730 (FIG. 27D), process 2740 (FIG. 27E), process 2800(FIG. 28), process 2900 (FIG. 29), process 3000 (FIG. 30), process 3100(FIG. 31), process 3200 (FIG. 32), and/or process 3300 (FIG. 33) mayinclude one or more of the characteristics of the various methodsdescribed above with reference to process 2750. For brevity, thesedetails are not repeated below.

It should be understood that the particular order in which theoperations in FIG. 27F have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of process2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process2300 (FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process2600 (FIG. 26), process 2700 (FIG. 27A), process 2710 (FIG. 27B),process 2720 (FIG. 27C), process 2730 (FIG. 27D), process 2740 (FIG.27E), process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG.30), process 3100 (FIG. 31), process 3200 (FIG. 32), and process 3300(FIG. 33) may be incorporated with one another. Thus, the techniquesdescribed with respect to process 2750 may be relevant to process 2000(FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process 2300(FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process 2600(FIG. 26), process 2700 (FIG. 27A), process 2710 (FIG. 27B), process2720 (FIG. 27C), process 2730 (FIG. 27D), process 2740 (FIG. 27E),process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG. 30),process 3100 (FIG. 31), process 3200 (FIG. 32), and/or process 3300(FIG. 33).

FIG. 28 is a flow diagram illustrating process 2800 for providingcontext-specific user interfaces. In some embodiments, process 2800 maybe performed at an electronic device with a touch-sensitive displayconfigured to detect intensity of contacts, such as 500 (FIG. 5) or 1500(FIG. 15). Some operations in process 2800 may be combined, the order ofsome operations may be changed, and some operations may be omitted.Process 2800 provides for editing multiple aspects of variouscontext-specific user interfaces in a comprehensive yet easy-to-usemanner, thus conserving power and increasing battery life.

At block 2802, the device displays a user interface screen that includesa clock face (e.g., 1504). At block 2804, the device detects a contacton the display (contact has characteristic intensity; see, e.g., touch1508). At block 2806, a determination is made as to whether thecharacteristic intensity is above an intensity threshold. At block 2808,in accordance with a determination that the characteristic intensity isabove the intensity threshold, the device enters a clock face edit mode(see, e.g., screen 1510). In accordance with a determination that thecharacteristic intensity is not above the intensity threshold (where theclock face includes an affordance representing an application, and wherethe contact is on the affordance representing the application), thedevice may launch the application represented by the affordance. Atblock 2810, the device visually distinguishes the displayed clock faceto indicate edit mode (e.g., 1512). At block 2812, the device detects asecond contact on the display at the visually distinguished clock face(e.g., 1520). At block 2814, responsive at least in part to detectingthe second contact, the device visually indicates an element of theclock face for editing (e.g., 1534).

Note that details of the processes described above with respect toprocess 2800 (FIG. 28) are also applicable in an analogous manner to themethods described below. For example, process 2000 (FIG. 20), process2100 (FIG. 21), process 2200 (FIG. 22), process 2300 (FIG. 23), process2400 (FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26), process2700 (FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C),process 2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG.27F), process 2900 (FIG. 29), process 3000 (FIG. 30), process 3100 (FIG.31), process 3200 (FIG. 32), and/or process 3300 (FIG. 33) may includeone or more of the characteristics of the various methods describedabove with reference to process 2800. For brevity, these details are notrepeated below.

It should be understood that the particular order in which theoperations in FIG. 28 have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of process2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process2300 (FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process2600 (FIG. 26), process 2700 (FIG. 27A), process 2710 (FIG. 27B),process 2720 (FIG. 27C), process 2730 (FIG. 27D), process 2740 (FIG.27E), process 2750 (FIG. 27F), process 2900 (FIG. 29), process 3000(FIG. 30), process 3100 (FIG. 31), process 3200 (FIG. 32), and process3300 (FIG. 33) may be incorporated with one another. Thus, thetechniques described with respect to process 2800 may be relevant toprocess 2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22),process 2300 (FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25),process 2600 (FIG. 26), process 2700 (FIG. 27A), process 2710 (FIG.27B), process 2720 (FIG. 27C), process 2730 (FIG. 27D), process 2740(FIG. 27E), process 2750 (FIG. 27F), process 2900 (FIG. 29), process3000 (FIG. 30), process 3100 (FIG. 31), process 3200 (FIG. 32), and/orprocess 3300 (FIG. 33).

FIG. 29 is a flow diagram illustrating process 2900 for providingcontext-specific user interfaces. In some embodiments, process 2900 maybe performed at an electronic device with a touch-sensitive displayconfigured to detect intensity of contacts, such as 500 (FIG. 5) or 1600(FIGS. 16A-C). Some operations in process 2900 may be combined, theorder of some operations may be changed, and some operations may beomitted. Process 2900 provides for selecting context-specific userinterfaces in a comprehensive yet easy-to-use manner, thus conservingpower and increasing battery life.

At block 2902, the device displays a user interface screen that includesa clock face (e.g., 1604). At block 2904, the device detects a contacton the display (contact has characteristic intensity (e.g., 1606). Atblock 2906, a determination is made as to whether the characteristicintensity is above an intensity threshold. At block 2908, in accordancewith a determination that the characteristic intensity is above theintensity threshold, the device enters a clock face selection mode (see,e.g., screen 1610). In accordance with a determination that thecharacteristic intensity is not above the intensity threshold (where theclock face includes an affordance representing an application, and wherethe contact is on the affordance representing the application), thedevice may launch the application represented by the affordance. Atblock 2910, the device visually distinguishes the displayed clock faceto indicate selection mode (the clock face is centered on the display;see, e.g., 1612). At block 2912, the device detects a swipe on thedisplay at the visually distinguished clock face (e.g., 1618). At block2914, responsive at least in part to detecting the swipe, the devicecenters a second clock face on the display (e.g., 1616 on screen 1620).

Note that details of the processes described above with respect toprocess 2900 (FIG. 29) are also applicable in an analogous manner to themethods described below. For example, process 2000 (FIG. 20), process2100 (FIG. 21), process 2200 (FIG. 22), process 2300 (FIG. 23), process2400 (FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26), process2700 (FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C),process 2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG.27F), process 2800 (FIG. 28), process 3000 (FIG. 30), process 3100 (FIG.31), process 3200 (FIG. 32), and/or process 3300 (FIG. 33) may includeone or more of the characteristics of the various methods describedabove with reference to process 2900. For brevity, these details are notrepeated below.

It should be understood that the particular order in which theoperations in FIG. 29 have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of process2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process2300 (FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process2600 (FIG. 26), process 2700 (FIG. 27A), process 2710 (FIG. 27B),process 2720 (FIG. 27C), process 2730 (FIG. 27D), process 2740 (FIG.27E), process 2750 (FIG. 27F), process 2800 (FIG. 28), process 3000(FIG. 30), process 3100 (FIG. 31), process 3200 (FIG. 32), and process3300 (FIG. 33) may be incorporated with one another. Thus, thetechniques described with respect to process 2900 may be relevant toprocess 2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22),process 2300 (FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25),process 2600 (FIG. 26), process 2700 (FIG. 27A), process 2710 (FIG.27B), process 2720 (FIG. 27C), process 2730 (FIG. 27D), process 2740(FIG. 27E), process 2750 (FIG. 27F), process 2800 (FIG. 28), process3000 (FIG. 30), process 3100 (FIG. 31), process 3200 (FIG. 32), and/orprocess 3300 (FIG. 33).

FIG. 30 is a flow diagram illustrating process 3000 for providingcontext-specific user interfaces. In some embodiments, process 3000 maybe performed at an electronic device with a touch-sensitive displayconfigured to detect intensity of contacts, such as 500 (FIG. 5), 1500(FIG. 15), or 1600 (FIGS. 16A-C). Some operations in process 3000 may becombined, the order of some operations may be changed, and someoperations may be omitted. For example, FIG. 30 illustrates an exemplaryembodiment for accessing clock face selection and edit modes from asingle interface, but other orders of operation are possible. Process3000 provides for selecting and editing context-specific user interfacesin a comprehensive yet easy-to-use manner, thus conserving power andincreasing battery life.

At block 3002, the device displays a user interface screen that includesa clock face (e.g., 1502 and/or 1602). At block 3004, the device detectsa contact on the display (contact has characteristic intensity; see,e.g., 1508 and/or 1606). At block 3006, a determination is made as towhether the characteristic intensity is above an intensity threshold. Atblock 3008, in accordance with a determination that the characteristicintensity is above the intensity threshold, the device enters a clockface selection mode and visually distinguishes the displayed clock faceto indicate selection mode (the clock face is centered on the display;see, e.g., 1512 and/or 1612). In accordance with a determination thatthe characteristic intensity is not above the intensity threshold (wherethe clock face includes an affordance representing an application, andwhere the contact is on the affordance representing the application),the device may launch the application represented by the affordance. Atblock 3010, the device detects a swipe on the display at the visuallydistinguished clock face (e.g., 1618). At block 3012, responsive atleast in part to detecting the swipe, the device centers a second clockface on the display (e.g., 1616 on screen 1620). At block 3014, thedevice detects a contact on the touch-sensitive display at the displayedsecond clock face (e.g., 1520). At block 3016, responsive at least inpart to detecting the contact, the device enters a clock face edit modefor editing the second clock face (see, e.g., screen 1530).

Note that details of the processes described above with respect toprocess 3000 (FIG. 30) are also applicable in an analogous manner to themethods described below. For example, process 2000 (FIG. 20), process2100 (FIG. 21), process 2200 (FIG. 22), process 2300 (FIG. 23), process2400 (FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26), process2700 (FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C),process 2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG.27F), process 2800 (FIG. 28), process 2900 (FIG. 29), process 3100 (FIG.31), process 3200 (FIG. 32), and/or process 3300 (FIG. 33) may includeone or more of the characteristics of the various methods describedabove with reference to process 3000. For brevity, these details are notrepeated below.

It should be understood that the particular order in which theoperations in FIG. 30 have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For example, the device coulddetect a contact on the displayed first clock face before detecting theswipe. In this case, the device may enter clock face edit mode to editthe first clock face. For brevity, all of these details are not repeatedhere. Additionally, it should be noted that aspects of process 2000(FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process 2300(FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process 2600(FIG. 26), process 2700 (FIG. 27A), process 2710 (FIG. 27B), process2720 (FIG. 27C), process 2730 (FIG. 27D), process 2740 (FIG. 27E),process 2750 (FIG. 27F), process 2800 (FIG. 28), process 2900 (FIG. 29),process 3100 (FIG. 31), process 3200 (FIG. 32), and process 3300 (FIG.33) may be incorporated with one another. Thus, the techniques describedwith respect to process 2900 may be relevant to process 2000 (FIG. 20),process 2100 (FIG. 21), process 2200 (FIG. 22), process 2300 (FIG. 23),process 2400 (FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26),process 2700 (FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG.27C), process 2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750(FIG. 27F), process 2800 (FIG. 28), process 2900 (FIG. 29), process 3100(FIG. 31), process 3200 (FIG. 32), and/or process 3300 (FIG. 33).

FIG. 31 is a flow diagram illustrating process 3100 for providingcontext-specific user interfaces. In some embodiments, process 3100 maybe performed at an electronic device with a touch-sensitive display anda rotatable input mechanism, such as 500 (FIG. 5) or 1600 (FIGS. 17A and17B). Some operations in process 3100 may be combined, the order of someoperations may be changed, and some operations may be omitted. Process3100 provides for setting a user reminder in various context-specificuser interfaces in a less confusing and easy-to-access manner, thusconserving power and increasing battery life.

At block 3102, the device displays a user interface screen that includesa clock face (e.g., screen 1702) and an affordance on the clock face(affordance indicates first time of day; see, e.g., 1706). At block3104, the device detects a contact on the display. At block 3106,responsive at least in part to detecting the contact, the device entersa user interaction mode. At block 3108, while in user interaction mode,the device detects a movement of the rotatable input mechanism (e.g.,1708). At block 3110, responsive at least in part to detecting themovement, the device updates the affordance to indicate a second time ofday (e.g., 1714). At block 3112, the device detects a second contact atthe affordance (e.g., 1716). At block 3114, responsive at least in partto detecting the contact, the device sets a user reminder for the secondtime of day (e.g., 1748).

Note that details of the processes described above with respect toprocess 3100 (FIG. 31) are also applicable in an analogous manner to themethods described below. For example, process 2000 (FIG. 20), process2100 (FIG. 21), process 2200 (FIG. 22), process 2300 (FIG. 23), process2400 (FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26), process2700 (FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C),process 2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG.27F), process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG.30), process 3200 (FIG. 32), and/or process 3300 (FIG. 33) may includeone or more of the characteristics of the various methods describedabove with reference to process 3100. For brevity, these details are notrepeated below.

It should be understood that the particular order in which theoperations in FIG. 31 have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of process2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process2300 (FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process2600 (FIG. 26), process 2700 (FIG. 27A), process 2710 (FIG. 27B),process 2720 (FIG. 27C), process 2730 (FIG. 27D), process 2740 (FIG.27E), process 2750 (FIG. 27F), process 2800 (FIG. 28), process 2900(FIG. 29), process 3000 (FIG. 30), process 3200 (FIG. 32), and process3300 (FIG. 33) may be incorporated with one another. Thus, thetechniques described with respect to process 3100 may be relevant toprocess 2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22),process 2300 (FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25),process 2600 (FIG. 26), process 2700 (FIG. 27A), process 2710 (FIG.27B), process 2720 (FIG. 27C), process 2730 (FIG. 27D), process 2740(FIG. 27E), process 2750 (FIG. 27F), process 2800 (FIG. 28), process2900 (FIG. 29), process 3000 (FIG. 30), process 3200 (FIG. 32), and/orprocess 3300 (FIG. 33).

FIG. 32 is a flow diagram illustrating process 3200 for providingcontext-specific user interfaces. In some embodiments, process 3200 maybe performed at an electronic device with a touch-sensitive display,such as device 100 (FIG. 1A), 300 (FIG. 3), 500 (FIG. 5) or 1800 (FIGS.18A-18C). Some operations in process 3200 may be combined, the order ofsome operations may be changed, and some operations may be omitted.Process 3200 provides for launching an application directly from anapplication complication (which also provides application information)through various context-specific user interfaces, thus conserving powerand increasing battery life by easily linking various user applicationsand a timekeeping clock face.

At block 3202, the device displays a user interface screen that includesa clock face (e.g., 1804) and an affordance (affordance represents anapplication and displays a set of information from the application) as acomplication (e.g., 1806 and/or 1808). At block 3204, the device detectsa contact on the affordance (e.g., 1810 and/or 1812). At block 3206,responsive at least in part to detecting the contact, the devicelaunches the application represented by the affordance (see, e.g.,screen 1820 and/or 1830).

Note that details of the processes described above with respect toprocess 3200 (FIG. 32) are also applicable in an analogous manner to themethods described below. For example, process 2000 (FIG. 20), process2100 (FIG. 21), process 2200 (FIG. 22), process 2300 (FIG. 23), process2400 (FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26), process2700 (FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C),process 2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG.27F), process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG.30), process 3100 (FIG. 31), and/or process 3300 (FIG. 33) may includeone or more of the characteristics of the various methods describedabove with reference to process 3100. For brevity, these details are notrepeated below.

It should be understood that the particular order in which theoperations in FIG. 32 have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of process2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process2300 (FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process2600 (FIG. 26), process 2700 (FIG. 27A), process 2710 (FIG. 27B),process 2720 (FIG. 27C), process 2730 (FIG. 27D), process 2740 (FIG.27E), process 2750 (FIG. 27F), process 2800 (FIG. 28), process 2900(FIG. 29), process 3000 (FIG. 30), process 3100 (FIG. 31), and process3300 (FIG. 33) may be incorporated with one another. Thus, thetechniques described with respect to process 3200 may be relevant toprocess 2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22),process 2300 (FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25),process 2600 (FIG. 26), process 2700 (FIG. 27A), process 2710 (FIG.27B), process 2720 (FIG. 27C), process 2730 (FIG. 27D), process 2740(FIG. 27E), process 2750 (FIG. 27F), process 2800 (FIG. 28), process2900 (FIG. 29), process 3000 (FIG. 30), process 3100 (FIG. 31), and/orprocess 3300 (FIG. 33).

FIG. 33 is a flow diagram illustrating process 3300 for providingcontext-specific user interfaces. In some embodiments, process 3300 maybe performed at an electronic device with a touch-sensitive display,such as device 100 (FIG. 1A), 300 (FIG. 3), 500 (FIG. 5) or 1900 (FIG.19). Some operations in process 3300 may be combined, the order of someoperations may be changed, and some operations may be omitted. Process3300 provides a simple means by which to access various context-specificuser interfaces, thus conserving power and increasing battery life.

At block 3302, the device displays a user interface screen that includesa plurality of affordances (a first affordance in the pluralityindicates a clock face, which includes an indication of time and anoutline; see, e.g., screen 1902 and affordance 1906). At block 3304, thedevice detects a contact on first affordance (e.g., 1908). At block3306, responsive at least in part to detecting the contact, the devicesubstitutes the display of user interface screen with a second userinterface screen (substitution includes retaining the indication of timeor the outline at a larger size; see, e.g., screen 1930 with outline1932 and/or hour hand and minute hand 1934).

Note that details of the processes described above with respect toprocess 3300 (FIG. 33) are also applicable in an analogous manner to themethods described below. For example, process 2000 (FIG. 20), process2100 (FIG. 21), process 2200 (FIG. 22), process 2300 (FIG. 23), process2400 (FIG. 24), process 2500 (FIG. 25), process 2600 (FIG. 26), process2700 (FIG. 27A), process 2710 (FIG. 27B), process 2720 (FIG. 27C),process 2730 (FIG. 27D), process 2740 (FIG. 27E), process 2750 (FIG.27F), process 2800 (FIG. 28), process 2900 (FIG. 29), process 3000 (FIG.30), process 3100 (FIG. 31), and/or process 3200 (FIG. 32) may includeone or more of the characteristics of the various methods describedabove with reference to process 3300. For brevity, these details are notrepeated below.

It should be understood that the particular order in which theoperations in FIG. 33 have been described is exemplary and not intendedto indicate that the described order is the only order in which theoperations could be performed. One of ordinary skill in the art wouldrecognize various ways to reorder the operations described herein, aswell as excluding certain operations. For brevity, these details are notrepeated here. Additionally, it should be noted that aspects of process2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22), process2300 (FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25), process2600 (FIG. 26), process 2700 (FIG. 27A), process 2710 (FIG. 27B),process 2720 (FIG. 27C), process 2730 (FIG. 27D), process 2740 (FIG.27E), process 2750 (FIG. 27F), process 2800 (FIG. 28), process 2900(FIG. 29), process 3000 (FIG. 30), process 3100 (FIG. 31), and process3200 (FIG. 32) may be incorporated with one another. Thus, thetechniques described with respect to process 3300 may be relevant toprocess 2000 (FIG. 20), process 2100 (FIG. 21), process 2200 (FIG. 22),process 2300 (FIG. 23), process 2400 (FIG. 24), process 2500 (FIG. 25),process 2600 (FIG. 26), process 2700 (FIG. 27A), process 2710 (FIG.27B), process 2720 (FIG. 27C), process 2730 (FIG. 27D), process 2740(FIG. 27E), process 2750 (FIG. 27F), process 2800 (FIG. 28), process2900 (FIG. 29), process 3000 (FIG. 30), process 3100 (FIG. 31), and/orprocess 3200 (FIG. 32).

The operations in the information processing methods described above maybe implemented by running one or more functional modules in informationprocessing apparatus such as general purpose processors or applicationspecific chips. These modules, combinations of these modules, and/ortheir combination with general hardware (e.g., as described above withrespect to FIGS. 1A, 1B, 3, 5A, and 5B) are all included within thescope of the techniques described herein.

FIG. 34 shows exemplary functional blocks of an electronic device 3400that, in some embodiments, performs the features described above. Asshown in FIG. 34, an electronic device 3400 includes a display unit 3402configured to display graphical objects; a touch-sensitive surface unit3404 configured to receive user gestures; one or more RF units 3406configured to detect and communicate with external electronic devices;and a processing unit 3408 coupled to display unit 3402, touch-sensitivesurface unit 3404, and RF unit(s) 3406. In some embodiments, processingunit 3408 is configured to support an operating system 3410 and anapplications unit 3412. In some embodiments, operating system 3410 isconfigured to launch applications with applications unit 3412 or enter adevice mode. In some embodiments, operating system 3410 is configured tolaunch an application, enter a clock face edit mode of the electronicdevice, enter a clock face selection mode of the electronic device, orenter a user interaction mode of the electronic device. In someembodiments, applications unit 3412 is configured to launch or runapplications with applications unit 3412. For example, applications unit3412 may be used for launching an application, running a launchedapplication, or setting a user reminder.

In some embodiments, the processing unit 3408 includes a displayenabling unit 3414, a detecting unit 3416, a determining unit 3418, andan accessing unit 3420. In some embodiments, the display enabling unit3414 is configured to cause a display of a user interface (or portionsof a user interface) in conjunction with the display unit 3402. Forexample, the display enabling unit 3414 may be used for displaying auser interface screen, updating a user interface screen, displaying aclock face, substituting one or more indications of an hourly timescalewith an indication of a first timescale for a stopwatch hand, animatinga stopwatch hand, rotating a simulation of the Earth (or Moon, or solarsystem), animating a user interface object, displaying an animatedreveal of a clock face, displaying a character user interface object,updating a displayed character user interface object (e.g., updating adisplayed character user interface object to indicate a second time orupdating a displayed character user interface object by changing avisual aspect of the displayed character user interface object),visually distinguishing a displayed clock face to indicate a clock faceedit mode, visually indicating an element of a clock face for editing,visually distinguishing a displayed clock face to indicate a clock faceselection mode, centering a clock face on the display, updating anaffordance to indicate a time of day, or substituting the display of afirst user interface screen with a second user interface screen. In someembodiments, the detecting unit 3416 is configured to detect and/orreceive user input, e.g., through the use of touch-sensitive surfaceunit 3404 or a rotatable input mechanism (e.g., 506 or 1540). Forexample, the detecting 3416 may be used for detecting a user input,receiving data representing a user input, receiving a user input,detecting a user movement of the device, detecting a contact on thetouch-sensitive display, detecting a swipe on the touch-sensitivedisplay, or detecting a movement of the rotatable input mechanism. Insome embodiments, the determining unit 3418 is configured to makedeterminations. For example, determining unit 3418 may be used fordetermining whether characteristic intensity of a contact on thetouch-sensitive display is above an intensity threshold or determiningwhether an event meets a condition. In some embodiments, the accessingunit 3420 is configured to access and/or select information. Forexample, accessing unit 3420 may be used for accessing a folder,selecting an image from the folder, accessing data representing apreviously displayed animated sequence, or selecting an animatedsequence. The units of FIG. 34 may be used to implement the varioustechniques and methods described above with respect to FIGS. 6-19.

The functional blocks of the device 3400 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 34 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

In accordance with some embodiments, FIG. 35 shows an exemplaryfunctional block diagram of an electronic device 3500 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 3500 are configured to perform the techniques described above.The functional blocks of the device 3500 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 35 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 35, an electronic device 3500 includes a display unit3502 configured to display a graphic user interface, optionally, atouch-sensitive surface unit 3504 configured to receive contacts,optionally, a location sensing unit 3518 configured to sense location,optionally, a movement detection unit 3520, and a processing unit 3506coupled to the display unit 3502, optionally, the touch-sensitivesurface unit 3504, optionally, the location sensing unit 3518, andoptionally, the movement detection unit 3520. In some embodiments, theprocessing unit 3506 includes a receiving unit 3508, a display enablingunit 3510, an update enabling unit 3512, an accessing unit 3514, and ananimation enabling unit 3516.

The processing unit 3506 is configured to receive (e.g., with receivingunit 3508) data representing a user input, and in response to receivingthe data: enable display (e.g., with display enabling unit 3510), on thedisplay unit (e.g., display unit 3502), of a user interface screen, theuser interface screen including a clock face indicating a first time,wherein the first time precedes a current time; and enable update (e.g.,with update enabling unit 3512), on the display unit (e.g., display unit3502), of the user interface screen by enabling animation (e.g., withanimation enabling unit 3516), on the display unit (e.g., display unit3502), of the clock face to transition from indicating the first time toindicating the current time, wherein the animation represents thepassage of time from the first time to the current time.

In some embodiments, the processing unit 3506 is further configured toreceive (e.g., with receiving unit 3508) second data representing a timeof a previous user movement of electronic device 3500, wherein theprevious user movement of electronic device 3500 is before receipt ofthe data representing the user input, and wherein the time of theprevious user movement of electronic device 3500 is the first timeindicated by the clock face. In some embodiments, the first timeprecedes the current time by a first duration, and wherein the firstduration is a predetermined duration before the current time. In someembodiments, the predetermined duration is 5 hours. In some embodiments,the first time is a predetermined time of day. In some embodiments, theclock face is animated for a period of time indicative of the firstduration. In some embodiments, the clock face is animated for a periodof time independent of the first duration. In some embodiments, theclock face comprises a representation of a digital clock including anumerical indication of an hour and a numerical indication of a minute.In some embodiments, the clock face comprises a representation of ananalog clock including an hour hand and a minute hand. In someembodiments, enabling animation (e.g., with animation enabling unit3516) of the first user interface object (e.g., on the user interfacescreen displayed on display unit 3502) comprises rotating one or more ofthe hour hand and the minute hand in a clockwise motion on-screen. Insome embodiments, the processing unit 3506 is further configured toaccess (e.g., with accessing unit 3514) an image of a scene, wherein theimage of the scene is representative of the time indicated by the clockface; and enable display (e.g., with display enabling unit 3510), on thedisplay unit (e.g., display unit 3502), of the image as a background onthe user interface screen. In some embodiments, the image of the sceneis an image captured at substantially the same time of day as the timeindicated by the clock face. In some embodiments, the processing unit3506 is further configured to access (e.g., with accessing unit 3514) afirst image of a scene, wherein the first image is representative of thefirst time; and access (e.g., with accessing unit 3514) a second imageof the scene, wherein the second image is representative of the currenttime; and in response to receiving (e.g., with receiving unit 3508) thedata representing the user input: enable successive display (e.g., withdisplay enabling unit 3510), on the display unit (e.g., display unit3502), of the first image of the scene and the second image of thescene, the successive display indicating the passage of time from thefirst time to the current time. In some embodiments, the first image ofthe scene and the second image of the scene are displayed as backgroundson the user interface screen. In some embodiments, the processing unit3506 is further configured to access (e.g., with accessing unit 3514) asequence of images of a scene, the sequence of images including: a firstimage of the scene, wherein the first image of the scene isrepresentative of the first time; one or more second images of thescene, wherein the one or more second images are representative of oneor more times between the first time and the current time, and whereinthe one or more second images are after the first image of the scenewithin the sequence of images; and a third image of the scene, whereinthe third image of the scene is representative of the current time, andwherein the third image of the scene is after the one or more secondimages of the scene within the sequence of images; and in response toreceiving (e.g., with receiving unit 3508) the data representing theuser input: enable display (e.g., with display enabling unit 3510), onthe display unit (e.g., display unit 3502), of the sequence of images ofthe scene as an animated sequence, wherein displaying the sequence ofimages comprises enabling animation (e.g., with animation enabling unit3516) of the sequence of images to indicate the passage of time from thefirst time to the current time. In some embodiments, the sequence ofimages of the scene is displayed as an animated background on the userinterface screen. In some embodiments, the scene is user-designated. Insome embodiments, electronic device 3500 further comprises a locationsensing unit (e.g., location sensing unit 3730), processing unit 3506 iscoupled to the location sensing unit (e.g., location sensing unit 3730),and the processing unit 3506 is further configured to enable obtaining acurrent location of electronic device 3500 from the location sensor(e.g., location sensing unit 3518), wherein the first image representsthe first time at the current location, and wherein the second image orthe third image represents the current time at the current location. Insome embodiments, the processing unit 3506 is further configured toenable display (e.g., with display enabling unit 3510), on the displayunit (e.g., display unit 3502), of a user interface object on the userinterface screen at a first position, wherein the first position of theuser interface object is based on the first time. In some embodiments,the processing unit 3506 is further configured to enable animation(e.g., with animation enabling unit 3516), on the display unit (e.g.,display unit 3502), of the user interface object by moving the userinterface object from the first position to a second position on theuser interface screen, wherein the second position is based on thecurrent time, and wherein moving the user interface object from thefirst position to a second position indicates the passage of time fromthe first time to the current time. In some embodiments, the userinterface object is a graphical representation of a sun. In someembodiments, the user interface object is a graphical representation ofa moon. In some embodiments, the electronic device 3500 further includesa movement detection unit (e.g., movement detection unit 3520), theprocessing unit 3506 is coupled to the movement detection unit, and theprocessing unit 3506 is further configured to: detect a movement of theelectronic device (e.g., with movement detection unit 3520), wherein theuser input comprises the movement of the electronic device 3500. In someembodiments, the user input is a contact on the touch-sensitive surfaceunit (e.g., touch-sensitive surface unit 3504).

The operations described above with reference to FIG. 20 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.35. For example, receiving operation 2002, displaying operation 2004,and updating operation 2006 may be implemented by event sorter 170,event recognizer 180, and event handler 190. Event monitor 171 in eventsorter 170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

In accordance with some embodiments, FIG. 36 shows an exemplaryfunctional block diagram of an electronic device 3600 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 3600 are configured to perform the techniques described above.The functional blocks of the device 3600 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 36 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 36, an electronic device 3600 includes a display unit3602 configured to display a graphic user interface, optionally, atouch-sensitive surface unit 3604 configured to receive contacts,optionally, a rotatable input unit 3624 configured to receive rotatableinput (e.g., from a rotatable input mechanism), and a processing unit3606 coupled to the display unit 3602, optionally, the touch-sensitivesurface unit 3604, and optionally, the rotatable input unit 3624. Insome embodiments, the processing unit 3606 includes a receiving unit3608, a display enabling unit 3610, a substitution enabling unit 3612, acessation enabling unit 3614, an animation enabling unit 3616, alaunching unit 3618, a removal enabling unit 3620, and a translationenabling unit 3622.

The processing unit 3606 is configured to enable display (e.g., withdisplay enabling unit 3610), on the display unit (e.g., display unit3602), of a clock face that indicates current time, the clock faceincluding: a user interface object comprising an hour hand and a minutehand, wherein the user interface object indicates the current time; oneor more indications of an hourly timescale; and a stopwatch hand;receive data (e.g., with receiving unit 3608) representing a user input;and enable substitution (e.g., with substitution enabling unit 3612), onthe display unit (e.g., display unit 3602), of the one or moreindications of an hourly timescale with an indication of a firsttimescale for the stopwatch hand; and enable animation (e.g., withanimation enabling unit 3616), on the display unit (e.g., display unit3602), of the stopwatch hand to reflect passage of time.

In some embodiments, the processing unit 3606 is further configured to,while enabling animation (e.g., with animation enabling unit 3616), onthe display unit (e.g., display unit 3602), of the stopwatch hand toreflect the passage of time, receive second data (e.g., with receivingunit 3608) representing a second user input; and in response toreceiving the second data: enable cessation (e.g., with cessationenabling unit 3614), on the display unit (e.g., display unit 3602) ofthe animation of the stopwatch hand. In some embodiments, the processingunit 3606 is further configured to enable display (e.g., with displayenabling unit 3610), on the display unit (e.g., display unit 3602), of afirst affordance, the first affordance representing a start/stopfunction, wherein the first data representing the first user input andthe second data representing the second user input both representcontacts on the displayed first affordance. In some embodiments, theprocessing unit 3606 is further configured to enable display (e.g., withdisplay enabling unit 3610), on the display unit (e.g., display unit3602), of a second affordance, the second affordance representing a lapfunction; receive third data (e.g., with receiving unit 3608)representing a contact on the displayed second affordance, wherein thethird data is received after receiving the first data and beforereceiving the second data; and enable display (e.g., with displayenabling unit 3610), on the display unit (e.g., display unit 3602), of athird numerical indication of elapsed time between receiving the firstdata and receiving the third data. In some embodiments, the processingunit 3606 is further configured to enable display (e.g., with displayenabling unit 3610), on the display unit (e.g., display unit 3602), of athird affordance, the third affordance representing a stopwatchapplication; receive fourth data (e.g., with receiving unit 3608)representing a contact on the displayed third affordance; and inresponse to receiving the fourth data: launch (e.g., with launching unit3618) the stopwatch application. In some embodiments, the firsttimescale for the stopwatch hand is 60 seconds. In some embodiments, thefirst timescale for the stopwatch hand is 30 seconds. In someembodiments, the first timescale for the stopwatch hand is 6 seconds. Insome embodiments, the first timescale for the stopwatch hand is 3seconds. In some embodiments, movement of the stopwatch hand is animatedat a rate based on the first timescale for the stopwatch hand. In someembodiments, enabling substitution (e.g., with substitution enablingunit 3612), on the display unit (e.g., display unit 3602), of the one ormore indications of an hourly timescale with an indication of a firsttimescale for the stopwatch hand comprises: enabling removal (e.g., withremoval enabling unit 3620), on the display unit (e.g., display unit3602), of the one or more indications of the hourly timescale; enablingdisplay (e.g., with display enabling unit 3610), on the display unit(e.g., display unit 3602), of the indication of the first timescale forthe stopwatch hand; and enabling translation (e.g., with translationenabling unit 3622), on the display unit (e.g., display unit 3602), ofthe displayed indication of the first timescale for the stopwatch handin a rotational motion, wherein the rotational motion is in a clockwisedirection. In some embodiments, electronic device 3600 further comprisesa rotatable input unit (e.g., rotatable input unit 3624), wherein theprocessing unit is coupled to the rotatable input unit (e.g., rotatableinput unit 3624), and processing unit 3606 is further configured toreceive fifth data representing a rotatable input from the rotatableinput unit (e.g., with rotatable input unit 3624); and enablesubstitution (e.g., with substitution enabling unit 3612), on thedisplay unit (e.g., display unit 3602) of the indication of the firsttimescale for the stopwatch hand with an indication of a secondtimescale for the stopwatch hand, wherein the second timescale isdifferent from the first timescale. In some embodiments, enablingsubstitution (e.g., with substitution enabling unit 3612), on thedisplay unit (e.g., display unit 3602) of the indication of the firsttimescale for the stopwatch hand with the indication of the secondtimescale for the stopwatch hand comprises: enabling removal (e.g., withremoval enabling unit 3620), on the display unit (e.g., display unit3602), of the indication of the first timescale for the stopwatch hand;enabling display (e.g., with display enabling unit 3610), on the displayunit (e.g., display unit 3602) of the indication of the second timescalefor the stopwatch hand; and enabling translation (e.g., with translationenabling unit 3622), on the display unit (e.g., display unit 3602), ofthe displayed indication of the second timescale for the stopwatch handin a rotational motion, wherein the rotational motion is in a clockwisedirection. In some embodiments, the processing unit 3606 is furtherconfigured to after receiving the first data representing the first userinput: enable animation (e.g., with animation enabling unit 3616), onthe display unit (e.g., display unit 3602), of the stopwatch hand torepresent a rotational motion about an origin; and enable cessation(e.g., with cessation enabling unit 3614), on the display unit (e.g.,display unit 3602), of the animation to display the stopwatch hand at aposition at π/2 radians relative to the rotational motion about theorigin.

The operations described above with reference to FIG. 21 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.36. For example, displaying operation 2102, receiving operation 2104,and substituting operation 2106 may be implemented by event sorter 170,event recognizer 180, and event handler 190. Event monitor 171 in eventsorter 170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

In accordance with some embodiments, FIG. 37 shows an exemplaryfunctional block diagram of an electronic device 3700 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 3700 are configured to perform the techniques described above.The functional blocks of the device 3700 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 37 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 37, an electronic device 3700 includes a display unit3702 configured to display a graphic user interface, optionally, atouch-sensitive surface unit 3704 configured to receive contacts,optionally, a rotatable input unit 3728 configured to receive rotatableinput (e.g., from a rotatable input mechanism), optionally, a locationsensing unit 3730 configured to sense location, and a processing unit3706 coupled to the display unit 3702, optionally, the touch-sensitivesurface unit 3704, optionally, the rotatable input unit 3728, andoptionally, the location sensing unit 3730. In some embodiments, theprocessing unit 3706 includes a receiving unit 3708, a display enablingunit 3710, a rotation enabling unit 3712, an update enabling unit 3714,a detecting unit 3716, an animation enabling unit 3718, a visualdistinguishment enabling unit 3720, a removal enabling unit 3722, areplacement enabling unit 3724, and a determining unit 3726.

The processing unit 3706 is configured to enable display (e.g., withdisplay enabling unit 3710), on the display unit (e.g., display unit3702), of a user interface screen, the user interface screen including:a first affordance representing a simulation of a first region of theEarth as illuminated by the Sun at a current time; and a secondaffordance indicating the current time; receive (e.g., with receivingunit 3708) a user input; and in response to receiving the user input:enable rotation (e.g., with rotation enabling unit 3712), on the displayunit (e.g., display unit 3702), of the simulation of the Earth todisplay a second region of the Earth as illuminated by the Sun at thecurrent time.

In some embodiments, the first affordance representing the simulation ofthe first region of the Earth as illuminated by the Sun at the currenttime comprises a representation of a solar terminator. In someembodiments, the user input comprises a swipe on the touch-sensitivesurface unit (e.g., touch-sensitive surface unit 3704) in a first swipedirection. In some embodiments, the simulation of the first region ofthe Earth is rotated in a first direction of rotation, and theprocessing unit 3706 is further configured to: receive (e.g., withreceiving unit 3708) a second user input; and in response to receivingthe second user input: enable rotation (e.g., with rotation enablingunit 3712), on the display unit (e.g., display unit 3702), of thesimulation of the first region of the Earth in a second direction ofrotation, wherein the second direction of rotation and the firstdirection of rotation are different. In some embodiments, the seconduser input comprises a swipe on the touch-sensitive surface unit (e.g.,touch-sensitive surface unit 3704) in a second swipe direction, and thefirst swipe direction and the second swipe direction are different. Insome embodiments, electronic device 3700 further comprises a rotatableinput unit (e.g., rotatable input unit 3728), wherein the processingunit 3706 is coupled to the rotatable input unit, and wherein theprocessing unit 3706 is further configured to: receive a third userinput representing a rotatable input from the rotatable input unit(e.g., rotatable input unit 3728) and in response to receiving the thirduser input: enable update (e.g., with update enabling unit 3714), on thedisplay unit (e.g., display unit 3702), of the first affordance torepresent a simulation of the first region of the Earth as illuminatedby the Sun at a non-current time. In some embodiments, the processingunit 3706 is further configured to: enable update (e.g., with updateenabling unit 3714), on the display unit (e.g., display unit 3702), ofthe second affordance to indicate the non-current time. In someembodiments, electronic device 3700 further comprises a location sensingunit (e.g., location sensing unit 3730), wherein the processing unit3706 is coupled to the location sensing unit, and wherein the processingunit 3706 is further configured to: before displaying the user interfacescreen, obtain a current location of electronic device 3700 from thelocation sensing unit (e.g., location sensing unit 3730), wherein thedisplayed first region of the Earth represented by the first affordanceindicates the current location of electronic device 3700. In someembodiments, the processing unit 3706 is further configured to: detect(e.g., with detecting unit 3716) a user movement of electronic device3700; and in response to detecting the user movement: enable animation(e.g., with animation enabling unit 3718), on the display unit (e.g.,display unit 3702), of the first affordance representing the simulationof the Earth by translating the first affordance on-screen towards thecenter of the displayed user interface screen. In some embodiments, theprocessing unit 3706 is further configured to: enable display (e.g.,with display enabling unit 3710), on the display unit (e.g., displayunit 3702), of a third affordance, the third affordance representing amoon; detect (e.g., with detecting unit 3716) a contact on the displayedthird affordance on the touch-sensitive surface unit (e.g.,touch-sensitive surface unit 3704), and in response to detecting thecontact: enable update (e.g., with update enabling unit 3714), on thedisplay unit (e.g., display unit 3702), of the user interface screen,wherein enabling update of the display of the user interface screencomprises: enabling display (e.g., with display enabling unit 3710), onthe display unit (e.g., display unit 3702), of a fourth affordancerepresenting a simulation of the Moon, the fourth affordancerepresenting a simulation of the Moon as seen from the Earth at thecurrent time; and enabling display (e.g., with display enabling unit3710), on the display unit (e.g., display unit 3702), of a fifthaffordance indicating the current time. In some embodiments, enablingupdate (e.g., with update enabling unit 3714), on the display unit(e.g., display unit 3702), of the user interface screen comprisesenabling animation (e.g., with animation enabling unit 3718), on thedisplay unit (e.g., display unit 3702), of the first affordancerepresenting the simulation of the first region of the Earth asilluminated by the Sun by zooming out. In some embodiments, theprocessing unit 3706 is further configured to: receive (e.g., withreceiving unit 3708) a fourth user input; and in response to receivingthe fourth user input: enable rotation (e.g., with rotation enablingunit 3712), on the display unit (e.g., display unit 3702), of thesimulation of the Moon to display the Moon as seen from the Earth at anon-current time; and enable update (e.g., with update enabling unit3714), on the display unit (e.g., display unit 3702), of the fifthaffordance to indicate the non-current time. In some embodiments, thefourth user input comprises a swipe on the touch-sensitive surface unit(e.g., touch-sensitive surface unit 3704) in a first swipe direction. Insome embodiments, the simulation of the Moon as seen from the Earth isrotated in a first direction of rotation, and the processing unit 3706is further configured to: receive (e.g., with receiving unit 3708) afifth user input; and in response to receiving the fifth user input:enable rotation (e.g., with rotation enabling unit 3712), on the displayunit (e.g., display unit 3702), of the simulation of the Moon as seenfrom the Earth in a second direction of rotation, wherein the seconddirection of rotation and the first direction of rotation are different.In some embodiments, the fifth user input comprises a swipe on thetouch-sensitive surface unit (e.g., touch-sensitive surface unit 3704)in a second swipe direction, and the first swipe direction and thesecond swipe direction are different. In some embodiments, electronicdevice 3700 further comprises a rotatable input unit (e.g., rotatableinput unit 3728), the processing unit 3706 is coupled to the rotatableinput unit, and receiving the fourth user input comprises receiving arotatable input from the rotatable input unit (e.g., rotatable inputunit 3728) in a first direction of rotation. In some embodiments,electronic device 3700 further comprises a rotatable input unit (e.g.,rotatable input unit 3728), the processing unit 3706 is coupled to therotatable input unit, and the simulation of the Moon as seen from theEarth is rotated in a first direction of rotation, wherein theprocessing unit is further configured to: receive (e.g., with receivingunit 3708) a sixth user input; and in response to receiving the sixthuser input: enable rotation (e.g., with rotation enabling unit 3712), onthe display unit (e.g., display unit 3702), of the simulation of theMoon as seen from the Earth in a second direction of rotation, whereinthe second direction of rotation and the first direction of rotation aredifferent. In some embodiments, the sixth user input comprises arotatable input from the rotatable input unit (e.g., rotatable inputunit 3728) in a second direction of rotation, and wherein the firstdirection of rotation and the second direction of rotation aredifferent. In some embodiments, the processing unit 3706 is furtherconfigured to: detect (e.g., with detecting unit 3716) a user double tapon the touch-sensitive surface unit (e.g., touch-sensitive surface unit3704), the user double tap comprising a first contact on thetouch-sensitive surface unit and a second contact on the touch-sensitivesurface unit; determine (e.g., with determining unit 3726) whether thefirst contact and the second contact were received within apredetermined interval; and in response to detecting the user doubletap, and in accordance with a determination that the first contact andthe second contact were received within the predetermined interval:enable display (e.g., with display enabling unit 3710), on the displayunit (e.g., display unit 3702), of additional lunar information. In someembodiments, the processing unit 3706 is further configured to: enabledisplay (e.g., with display enabling unit 3710), on the display unit(e.g., display unit 3702), of a sixth affordance on the touch-sensitivesurface unit (e.g., touch-sensitive surface unit 3704), the sixthaffordance representing a solar system; detect (e.g., with detectingunit 3716) a contact on the displayed sixth affordance, and in responseto detecting the contact: enable update (e.g., with update enabling unit3714), on the display unit (e.g., display unit 3702), of the userinterface screen, wherein enabling update (e.g., with update enablingunit 3714), on the display unit (e.g., display unit 3702), of the userinterface screen comprises: enabling display (e.g., with displayenabling unit 3710), on the display unit (e.g., display unit 3702), of aseventh affordance representing a solar system, the seventh affordancecomprising representations of the Sun, the Earth, and one or morenon-Earth planets at their respective positions at a current time; andenabling display (e.g., with display enabling unit 3710), on the displayunit (e.g., display unit 3702), of an eighth affordance indicating thecurrent time. In some embodiments, enabling update (e.g., with updateenabling unit 3714), on the display unit (e.g., display unit 3702), ofthe user interface screen comprises enabling animation (e.g., withanimation enabling unit 3718), on the display unit (e.g., display unit3702), of the first affordance representing the simulation of the firstregion of the Earth as illuminated by the Sun or enabling animation(e.g., with animation enabling unit 3718), on the display unit (e.g.,display unit 3702), of the fourth affordance representing a simulationof the Moon as seen from the Earth by zooming out. In some embodiments,the processing unit 3706 is further configured to: receive (e.g., withreceiving unit 3708) a seventh user input; and in response to receivingthe seventh user input: enable update (e.g., with update enabling unit3714), on the display unit (e.g., display unit 3702), of the seventhaffordance to depict respective positions of the Sun, the Earth, and theone or more non-Earth planets for a non-current time, wherein updatingthe seventh affordance comprises rotating the Earth and the one or morenon-Earth planets about the Sun; and enable update (e.g., with updateenabling unit 3714), on the display unit (e.g., display unit 3702), ofthe eighth affordance to indicate the non-current time. In someembodiments, the seventh user input comprises a swipe on thetouch-sensitive surface unit (e.g., touch-sensitive surface unit 3704)in a first swipe direction. In some embodiments, the Earth and the oneor more non-Earth planets are rotated about the Sun in a first directionof rotation, and the processing unit 3706 is further configured to:receive (e.g., with receiving unit 3708) an eighth user input; and inresponse to receiving the eighth user input: enable rotation (e.g., withrotation enabling unit 3712), on the display unit (e.g., display unit3702), of the Earth and the one or more non-Earth planets about the Sunin a second direction of rotation, wherein the second direction ofrotation and the first direction of rotation are different. In someembodiments, the eighth user input comprises a swipe on thetouch-sensitive surface unit (e.g., touch-sensitive surface unit 3704)in a second swipe direction, and wherein the first swipe direction andthe second swipe direction are different. In some embodiments,electronic device 3700 further comprises a rotatable input unit (e.g.,rotatable input unit 3728), the processing unit 3706 is coupled to therotatable input unit (e.g., rotatable input unit 3728), and receivingthe seventh user input comprises receiving a rotatable input from therotatable input unit (e.g., rotatable input unit 3728) in a firstdirection of rotation. In some embodiments, electronic device 3700further comprises a rotatable input unit (e.g., rotatable input unit3728), the processing unit 3706 is coupled to the rotatable input unit,wherein the Earth and the one or more non-Earth planets are rotatedabout the Sun in a first direction of rotation, and the processing unit3706 is further configured to: receive (e.g., with receiving unit 3708)a ninth user input; and in response to receiving the ninth user input:enable rotation (e.g., with rotation enabling unit 3712), on the displayunit (e.g., display unit 3702), of the Earth and the one or morenon-Earth planets about the Sun in a second direction of rotation,wherein the second direction of rotation and the first direction ofrotation are different. In some embodiments, the ninth user inputcomprises a rotatable input from the rotatable input unit (e.g.,rotatable input unit 3728) in a second direction of rotation, andwherein the first direction of rotation and the second direction ofrotation are different. In some embodiments, the representation of theEarth further comprises a representation of the orbit of the Eartharound the Sun, and wherein the representation of the one or morenon-Earth planets further comprises a representation of the orbit of theone or more non-Earth planets around the Sun. In some embodiments, theprocessing unit 3706 is further configured to: receive (e.g., withreceiving unit 3708) a tenth user input comprising a contact on thetouch-sensitive surface unit (e.g., touch-sensitive surface unit 3704),wherein the contact is associated with the representation of the Earthor the representation of the one or more non-Earth planets, the contacton the touch-sensitive surface unit having an associated duration; whilecontinuing to receive the contact, determine (e.g., with determiningunit 3726) whether the duration of the contact exceeds a predeterminedthreshold; in response to receiving the tenth user input, and inaccordance with a determination that the duration of the contact exceedsthe predetermined threshold: enable visual distinguishment (e.g., withvisual distinguishment enabling unit 3720), on the display unit (e.g.,display unit 3702), of the representation of the Earth or therepresentation of the one or more non-Earth planets associated with thecontact; detect (e.g., with detecting unit 3716) a break in the contact;and in response to detecting the break in the contact: enable display(e.g., with display enabling unit 3710), on the display unit (e.g.,display unit 3702), of information about the Earth or the one or morenon-Earth planets associated with the contact. In some embodiments, theprocessing unit 3706 is further configured to: after enabling display,on the display unit, of the information about the Earth or the one ormore non-Earth planets associated with the contact, receive (e.g., withreceiving unit 3708) an eleventh user input; determine (e.g., withdetermining unit 3732) whether the eleventh user input represents a tapor a swipe on the touch-sensitive surface unit (e.g., touch-sensitivesurface unit 3704); in accordance with a determination that the eleventhuser input represents a tap: enable removal (e.g., with removal enablingunit 3724), on the display unit (e.g., display unit 3702), of thedisplayed information about the Earth or the one or more non-Earthplanets; and in accordance with a determination that the eleventh userinput represents a swipe: enable replacement (e.g, with replacementenabling unit 3724), on the display unit (e.g., display unit 3702), ofthe displayed information about the Earth or the one or more non-Earthplanets with information about a second planet selected from the groupconsisting of the Earth and the one or more non-Earth planets, whereinthe second planet is not the planet associated with the contact.

The operations described above with reference to FIG. 22 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.37. For example, displaying operation 2202, receiving operation 2204,and rotating operation 2206 may be implemented by event sorter 170,event recognizer 180, and event handler 190. Event monitor 171 in eventsorter 170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

In accordance with some embodiments, FIG. 38 shows an exemplaryfunctional block diagram of an electronic device 3800 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 3800 are configured to perform the techniques described above.The functional blocks of the device 3800 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 38 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 38, an electronic device 3800 includes a display unit3802 configured to display a graphic user interface, optionally, atouch-sensitive surface unit 3804 configured to receive contacts,optionally, a rotatable input unit 3820 configured to receive rotatableinput (e.g., from a rotatable input mechanism), optionally, a locationsensing unit 3822 configured to sense location, optionally, an audiounit 3826, optionally, a haptic unit 3828, and a processing unit 3806coupled to the display unit 3802, optionally, the touch-sensitivesurface unit 3804, optionally, the rotatable input unit 3820,optionally, the location sensing unit 3822, optionally, the audio unit3826, and optionally, the haptic unit 3828. In some embodiments, theprocessing unit 3806 includes a receiving unit 3808, a display enablingunit 3810, a translation enabling unit 3812, an update enabling unit3814, a determining unit 3816, a setting unit 3818, and a detecting unit3824.

The processing unit 3806 is configured to enable display (e.g., withdisplay enabling unit 3810), on the display unit (e.g., display unit3802), of a user interface screen, the user interface screen comprising:a first portion of the user interface screen, the first portionindicating daytime; a second portion of the user interface screen, thesecond portion indicating nighttime; a user interface object, the userinterface object representing a sinusoidal wave with a periodrepresenting a day, wherein the sinusoidal wave indicates a path of theSun through the day, and wherein the sinusoidal wave is displayed in oneor more of the first portion and the second portion; a first affordancerepresenting the Sun, wherein the first affordance is displayed at afirst position on the displayed sinusoidal wave, the first positionindicating a current time of the day and whether the current time of theday is during daytime or nighttime; and a second affordance, the secondaffordance indicating the current time of day.

In some embodiments, electronic device 3800 further comprises a locationsensing unit (e.g., location sensing unit 3822), processing unit 3806 iscoupled to the location sensing unit (e.g., location sensing unit 3822),and processing unit 3806 is further configured to: obtain a currentlocation of the electronic device from the location sensing unit (e.g.,with location sensing unit 3822), wherein the ratio of the displayedfirst portion indicating daytime relative to the second portionindicating nighttime indicates daylight hours at the current location atthe current time. In some embodiments, amplitude of the sinusoidal waveis based on height of the Sun relative to horizon at the currentlocation and at the current time. In some embodiments, the processingunit 3806 is further configured to: enable display (e.g., with displayenabling unit 3810), on the display unit (e.g., display unit 3802), of aline on the user interface screen, wherein the line divides the firstportion of the user interface screen indicating daytime and the secondportion of the user interface screen indicating nighttime, wherein theline intersects the sinusoidal wave at a first point representingsunrise and at a second point representing sunset. In some embodiments,the processing unit 3806 is further configured to: receive (e.g., withreceiving unit 3808) a user contact on the touch-sensitive surface unit(e.g., touch-sensitive surface unit 3804) at the first affordance, thefirst affordance displayed at the first position on the displayedsinusoidal wave, the first position indicating the current time; whilecontinuing to receive the user contact, detect (e.g., with detectingunit 3824) movement (e.g., on touch-sensitive surface unit 3804) of theuser contact from the first position to a second position on thedisplayed sinusoidal wave without a break in contact of the user contacton the touch-sensitive surface unit, the second position on thedisplayed sinusoidal wave indicating a non-current time; and in responseto detecting the contact at the second position: enable translation(e.g., with translation enabling unit 3812), on the display unit (e.g.,display unit 3802), of the first affordance on-screen from the firstposition on the displayed sinusoidal wave to the second position on thedisplayed sinusoidal wave, wherein the translation tracks the displayedsinusoidal wave; and enable update (e.g., with update enabling unit3814), on the display unit (e.g., display unit 3802), of the secondaffordance to indicate the non-current time. In some embodiments, theprocessing unit 3806 is further configured to: in response to detectingthe contact at the first affordance: enable display (e.g., with displayenabling unit 3810), on the display unit (e.g., display unit 3802), of,on the user interface screen: a third user interface object, wherein thethird user interface object is displayed at the first point along thesinusoidal wave representing sunrise; and a fourth user interfaceobject, wherein the fourth user interface object is displayed at thesecond point along the sinusoidal wave representing sunset. In someembodiments, the processing unit 3806 is further configured to: inresponse to detecting (e.g., with detecting unit 3824) the contact atthe first affordance (e.g., on touch-sensitive surface unit 3804):enable display (e.g., with display enabling unit 3810), on the displayunit (e.g., display unit 3802), of, on the user interface screen: afifth user interface object, wherein the fifth user interface object isdisplayed along the sinusoidal wave at a third point representing dawn;and a sixth user interface object, wherein the sixth user interfaceobject is displayed along the sinusoidal wave at a fourth pointrepresenting dusk. In some embodiments, the processing unit 3806 isfurther configured to: detect (e.g., with detecting unit 3824) a breakin contact of the user contact on the touch-sensitive surface unit(e.g., touch-sensitive surface unit 3804), and in response to detectingthe break in contact of the user contact on the touch-sensitive surfaceunit: enable translation (e.g., with translation enabling unit 3812), onthe display unit (e.g., display unit 3802), of the first affordanceon-screen from the second position to the first position, wherein thetranslation tracks the displayed sinusoidal wave; and enable update(e.g., with update enabling unit 3814), on the display unit (e.g.,display unit 3802), of the second affordance to indicate the currenttime of day. In some embodiments, the first affordance representing thesun appears filled when the first affordance is displayed at a positionfully within the first portion of the user interface screen. In someembodiments, the first affordance representing the sun appears hollowwhen the first affordance is displayed at a position fully within thesecond portion of the user interface screen. In some embodiments, thefirst affordance representing the sun appears half-filled when the firstaffordance is displayed at a position intersecting both the firstportion and the second portion of the user interface screen. In someembodiments, the processing unit 3806 is further configured to:determine (e.g., with determining unit 3816) whether the position of thefirst affordance on the displayed sinusoidal wave intersects with aposition of the second affordance indicating the current time of day;and in accordance with a determination that the position of the firstaffordance on the displayed sinusoidal wave intersects with a positionof the second affordance indicating the current time of day: enabledisplay (e.g., with display enabling unit 3810), on the display unit(e.g., display unit 3802), of the second affordance at a second positionthat does not intersect the position of the displayed sinusoidal wave.In some embodiments, the processing unit 3806 is further configured to:detect (e.g., with detecting unit 3824) a user input; and in response todetecting the user input: enable display (e.g., with display enablingunit 3810), on the display unit (e.g., display unit 3802), of a seconduser interface screen, the second user interface screen comprising anindication of a time of sunrise and an indication of a time of sunset.In some embodiments, the electronic device 3800 further comprises arotatable input unit (e.g., rotatable input unit 3820), the processingunit 3806 is coupled to the rotatable input unit, and the processingunit 3806 is further configured to: detect (e.g., with detecting unit3824) a movement corresponding to a rotatable input from the rotatableinput unit (e.g., rotatable input unit 3820); and in response todetecting the movement: enable translation (e.g., with translationenabling unit 3812), on the display unit (e.g., display unit 3802), ofthe first affordance representing the Sun to a third position on thedisplayed sinusoidal wave, wherein the third position indicates a thirdtime of day, wherein the third time of day is not the current time ofday; detect (e.g., with detecting unit 3824) a contact on thetouch-sensitive surface unit (e.g., with touch-sensitive surface unit3804) on the displayed first affordance at the third position; and inresponse to detecting the contact: set (e.g., with setting unit 3818) auser reminder for the third time of day. In some embodiments, settingthe user reminder for the third time of day comprises: enabling display,on the display unit (e.g., display unit 3802), of a third affordance onthe display, the third affordance representing a user prompt to set analert for the third time of day.

In some embodiments, the processing unit 3806 is further configured toenable display (e.g., with display enabling unit 3810), on the displayunit (e.g., display unit 3802), of a visual alert for the third time ofday, and the user reminder for the third time of day comprises thevisual alert for the third time of day. In some embodiments, theelectronic device 3800 further comprises an audio unit (e.g., audio unit3826), the processing unit 3806 is coupled to the audio unit, theprocessing unit 3806 is further configured to enable an audio alert forthe third time of day via the audio unit (e.g., with audio unit 3826),and the user reminder for the third time of day comprises the audioalert for the third time of day. In some embodiments, the electronicdevice 3800 further comprises a haptic unit (e.g., haptic unit 3828),the processing unit 3806 is coupled to the haptic unit, the processingunit 3806 is further configured to enable a haptic alert for the thirdtime of day via the haptic unit (e.g., with haptic unit 3828), and theuser reminder for the third time of day comprises the haptic alert forthe third time of day.

The operations described above with reference to FIG. 23 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.38. For example, displaying operation 2302, optional receiving operation2304, and optional detecting operation 2306 may be implemented by eventsorter 170, event recognizer 180, and event handler 190. Event monitor171 in event sorter 170 detects a contact on touch-sensitive display112, and event dispatcher module 174 delivers the event information toapplication 136-1. A respective event recognizer 180 of application136-1 compares the event information to respective event definitions186, and determines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

In accordance with some embodiments, FIG. 39 shows an exemplaryfunctional block diagram of an electronic device 3900 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 3900 are configured to perform the techniques described above.The functional blocks of the device 3900 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 39 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 39, an electronic device 3900 includes a display unit3902 configured to display a graphic user interface, optionally, atouch-sensitive surface unit 3904 configured to receive contacts,optionally, a wireless communication unit 3912 configured to send and/orreceive wireless communication, and a processing unit 3906 coupled tothe display unit 3902, optionally, the touch-sensitive surface unit3904, and optionally, the wireless communication unit 3912. In someembodiments, the processing unit 3906 includes a receiving unit 3908 anda display enabling unit 3910.

The processing unit 3906 is configured to enable display (e.g., withdisplay enabling unit 3910), on the display unit (e.g., display unit3902), of a user interface screen, the user interface screen including:a background based on an image, the background comprising a plurality ofpixels, wherein a subset of the pixels are modified in appearancerelative to the image such that the subset of pixels represents one ormore of: a first user interface object indicating a date; and a seconduser interface object indicating a time of day.

In some embodiments, the subset of the pixels is modified by colorblending. In some embodiments, the subset of the pixels is modified bycolor blurring. In some embodiments, the subset of the pixels ismodified in appearance relative to the image such that the subset ofpixels represents the first user interface object indicating the date.In some embodiments, the subset of the pixels is modified in appearancerelative to the image such that the subset of pixels represents thesecond user interface object indicating the time of day. In someembodiments, one of the first user interface object indicating the dateand the second user interface object indicating the time of day is afirst color independent of the background. In some embodiments, theprocessing unit 3906 is further configured to: receive (e.g., withreceiving unit 3908) data representing a background color of thebackground at a position of the displayed first user interface object orthe displayed second user interface object, wherein the first color isdifferent from the background color at the position of the displayedfirst user interface object or the displayed second user interfaceobject. In some embodiments, the image is a photo. In some embodiments,the image is stored on the electronic device. In some embodiments,wherein the electronic device 3900 further comprises a wirelesscommunication unit (e.g., wireless communication unit 3912), wherein theprocessing unit 3906 is coupled to the wireless communication unit, andthe image is stored on an external device coupled to electronic device3900 via the wireless communication unit (e.g., wireless communicationunit 3912). In some embodiments, the processing unit 3906 is furtherconfigured to: before enabling display (e.g., with display enabling unit3910), on the display unit (e.g., display unit 3902), of the userinterface screen: enable receipt (e.g., with receiving unit 3908), viathe wireless communication unit (e.g., wireless communication unit 3912)of data representing the background from the external device. In someembodiments, the processing unit 3906 is further configured to: enablereceipt (e.g., with receiving unit 3908), via the wireless communicationunit (e.g., wireless communication unit 3912) of data representing acurrent background of the external device, and enable display (e.g.,with display enabling unit 3910), on the display unit (e.g., displayunit 3902), of a second user interface screen on the display, the seconduser interface screen including: a second background, wherein the secondbackground corresponds with the current background of the externaldevice, the second background comprising a second plurality of pixels,wherein a second subset of the pixels are modified in appearancerelative to the current background of the external device such that thesecond subset of pixels represents one or more of: a third userinterface object indicating the date; and a fourth user interface objectindicating the time of day.

The operations described above with reference to FIG. 24 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.39. For example, displaying operation 2402 and optional receivingoperation 2404 may be implemented by event sorter 170, event recognizer180, and event handler 190. Event monitor 171 in event sorter 170detects a contact on touch-sensitive display 112, and event dispatchermodule 174 delivers the event information to application 136-1. Arespective event recognizer 180 of application 136-1 compares the eventinformation to respective event definitions 186, and determines whethera first contact at a first location on the touch-sensitive surfacecorresponds to a predefined event or sub event, such as activation of anaffordance on a user interface. When a respective predefined event orsub-event is detected, event recognizer 180 activates an event handler190 associated with the detection of the event or sub-event. Eventhandler 190 may utilize or call data updater 176 or object updater 177to update the application internal state 192. In some embodiments, eventhandler 190 accesses a respective GUI updater 178 to update what isdisplayed by the application. Similarly, it would be clear to a personhaving ordinary skill in the art how other processes can be implementedbased on the components depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 40 shows an exemplaryfunctional block diagram of an electronic device 4000 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 4000 are configured to perform the techniques described above.The functional blocks of the device 4000 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 40 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 40, an electronic device 4000 includes a display unit4002 configured to display a graphic user interface, optionally, awireless communication unit 4004 configured to send and/or receivewireless communications, and a processing unit 4006 coupled to thedisplay unit 4002, and optionally, the wireless communication unit 4004.In some embodiments, device 4000 may further include a touch-sensitivesurface unit configured to receive contacts and coupled to theprocessing unit 4006. In some embodiments, the processing unit 4006includes a receiving unit 4008, a display enabling unit 4010, anaccessing unit 4012, a selecting unit 4014, an obtaining unit 4016, anda preventing unit 4018.

The processing unit 4006 is configured to access (e.g., with accessingunit 4012) a folder, the folder including two or more images; select(e.g., with selecting unit 4014) from the folder a first image; andenable display (e.g., with display enabling unit 4010), on the displayunit (e.g., display unit 4002), of a user interface screen, the userinterface screen comprising: a background based on the first image, thebackground comprising a plurality of pixels, wherein a subset of thepixels are modified in appearance relative to the image such that thesubset of pixels represents one or more of: a first user interfaceobject indicating a date; and a second user interface object indicatinga time of day.

In some embodiments, the subset of the pixels is modified by colorblending. In some embodiments, the subset of the pixels is modified bycolor blurring. In some embodiments, the subset of the pixels ismodified in appearance relative to the image such that the subset ofpixels represents the first user interface object indicating the date.In some embodiments, the subset of the pixels is modified in appearancerelative to the image such that the subset of pixels represents thesecond user interface object indicating the time of day. In someembodiments, one of the first user interface object indicating the dateand the second user interface object indicating the time of day is afirst color independent of the background. In some embodiments, theprocessing unit 4006 is further configured to: receive (e.g., withreceiving unit 4008) data representing a background color of thebackground at a position of the displayed first user interface object orthe displayed second user interface object, wherein the first color isdifferent from the background color at the position of the displayedfirst user interface object or the displayed second user interfaceobject. In some embodiments, the processing unit 4006 is furtherconfigured to: after enabling display, on the display unit, of the firstuser interface screen, receive (e.g., with receiving unit 4008) firstdata representing a user input, and in response to receiving the firstdata representing the user input: obtain (e.g., with obtaining unit4016) second data representing the displayed first background; select(e.g., with selecting unit 4014) a second image from the folder, whereinthe second image is different from the first image; and enable display(e.g., with display enabling unit 4010), on the display unit (e.g.,display unit 4002), of a second user interface screen, the second userinterface screen comprising: a second background based on the secondimage, the second background comprising a second plurality of pixels,wherein a second subset of the pixels are modified in appearancerelative to the second image such that the second subset of pixelsrepresents one or more of: a third user interface object indicating adate; and a fourth user interface object indicating a time of day. Insome embodiments, the processing unit 4006 is further configured to:receive (e.g., with receiving unit 4008) data representing a userprohibition of a third image from the folder; and in response toreceiving the data: prevent (e.g., with preventing unit 4018) thedisplay, on the display unit (e.g., display unit 4002), of the thirdimage as a third background in response to a future user input. In someembodiments, at least one of the first background, the secondbackground, and the third background is a photo. In some embodiments,the folder is stored on the electronic device 4000. In some embodiments,the electronic device 4000 further includes a wireless communicationunit (e.g., wireless communication unit 4004), the processing unit 4006is coupled to the wireless communication unit, and the folder is storedon an external device coupled to the electronic device 4000 via thewireless communication unit (e.g., wireless communication unit 4004). Insome embodiments, accessing the folder comprises: receiving (e.g., withreceiving unit 4008), via the wireless communication unit (e.g.,wireless communication unit 4004), data representing at least one of thetwo or more backgrounds.

The operations described above with reference to FIG. 25 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.40. For example, accessing operation 2502, selecting operation 2504, anddisplaying operation 2506 may be implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

In accordance with some embodiments, FIG. 41 shows an exemplaryfunctional block diagram of an electronic device 4100 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 4100 are configured to perform the techniques described above.The functional blocks of the device 4100 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 41 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 41, an electronic device 4100 includes a display unit4102 configured to display a graphic user interface, optionally, atouch-sensitive surface unit 4104 configured to receive contacts,optionally, a movement detection unit 4120 configured to detectmovement, and a processing unit 4106 coupled to the display unit 4102,optionally, the touch-sensitive surface unit 4104 and optionally, themovement detection unit 4120. In some embodiments, the processing unit4106 includes a detecting unit 4108, a display enabling unit 4110, ananimation enabling unit 4112, a selecting unit 4114, an accessing unit4116, and a substitution enabling unit 4118.

The processing unit 4106 is configured to detect (e.g., with detectingunit 4108) a user input, wherein the user input is detected at a firsttime, and in response to detecting the user input: enable display (e.g.,with display enabling unit 4110), on the display unit (e.g., displayunit 4102), of a user interface screen, the user interface screenincluding: a first user interface object indicating the first time; anda second user interface object; and enable animation (e.g., withanimation enabling unit 4112), on the display unit (e.g., display unit4102), of the second user interface object, the animation comprising asequential display of a first animated sequence, a second animatedsequence after the first animated sequence, and a third animatedsequence after the second animated sequence, wherein the first animatedsequence, the second animated sequence, and the third animated sequenceare different; after enabling animation of the second user interfaceobject, detect (e.g., with detecting unit 4108) a second user input,wherein the second user input is detected at a second time, wherein thesecond time is after the first time, and in response to detecting thesecond user input: access (e.g., with accessing unit 4116) datarepresenting the previously displayed second animated sequence; select(e.g., with selecting unit 4114) a fourth animated sequence, wherein thefourth animated sequence is different from the first animated sequenceand the second animated sequence; enable display (e.g., with displayenabling unit 4110), on the display unit (e.g., display unit 4102), of asecond user interface screen, the second user interface screenincluding: the first user interface object, wherein the first userinterface object is updated to indicate the second time; and a thirduser interface object related to the second user interface object; andenable animation (e.g., with animation enabling unit 4112), on thedisplay unit (e.g., display unit 4102), of the third user interfaceobject, the animation comprising a sequential display of the firstanimated sequence, the fourth animated sequence after the first animatedsequence, and the third animated sequence after the fourth animatedsequence.

In some embodiments, the third animated sequence is based on a reversesequence of the first animated sequence. In some embodiments, theelectronic device 4100 further comprises a movement detection unit(e.g., movement detection unit 4120), wherein the processing unit 4106is coupled to the movement detection unit, and wherein the processingunit 4106 is further configured to enable detection of a movement of theelectronic device via the movement detection unit (e.g., movementdetection unit 4120), and wherein the user input represents a usermovement of the electronic device 4100. In some embodiments, theelectronic device 4100 further comprises a movement detection unit(e.g., movement detection unit 4120), wherein the processing unit 4106is coupled to the movement detection unit, and wherein the processingunit 4106 is further configured to enable detection of a movement of theelectronic device via the movement detection unit (e.g., movementdetection unit 4120), and wherein the second user input represents asecond user movement of the electronic device 4100. In some embodiments,the second user interface object and the third user interface object arethe same. In some embodiments, the third user interface object is areflection of the second user interface object. In some embodiments, thefourth animated sequence comprises a reflection of the second animatedsequence about a horizontal axis. In some embodiments, the fourthanimated sequence comprises a reflection of the second animated sequenceabout a vertical axis. In some embodiments, the processing unit 4106 isfurther configured to: detect (e.g., using detecting unit 4108) acontact on the touch-sensitive surface unit (e.g., touch-sensitivesurface unit 4104), and in response to detecting the contact: enablesubstitution (e.g., with substitution enabling unit 4118), on thedisplay unit (e.g., display unit 4102), of the second user interfaceobject or the third user interface object with a display, on the displayunit (e.g., display unit 4102), of a fourth user interface object,wherein the fourth user interface object is related to the second andthe third user interface objects. In some embodiments, the first userinterface object comprises a representation of a digital clock includinga numerical indication of an hour and a numerical indication of aminute. In some embodiments, the first time is a current time.

The operations described above with reference to FIG. 26 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.41. For example, detecting operation 4102, displaying operation 4104,and animating operation 4106 may be implemented by event sorter 170,event recognizer 180, and event handler 190. Event monitor 171 in eventsorter 170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

In accordance with some embodiments, FIG. 42 shows an exemplaryfunctional block diagram of an electronic device 4200 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 4200 are configured to perform the techniques described above.The functional blocks of the device 4200 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 42 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 42, an electronic device 4200 includes a display unit4202 configured to display a graphic user interface, optionally, atouch-sensitive surface unit 4204 configured to receive contacts,optionally, a movement detection unit 4220 configured to detectmovement, and a processing unit 4206 coupled to the display unit 4202,optionally, the touch-sensitive surface unit 4204 and optionally, themovement detection unit 4220. In some embodiments, the processing unit4206 includes a detecting unit 4208, a display enabling unit 4210, alaunching unit 4212, an update enabling unit 4214, a receiving unit4216, and a generating unit 4218.

The processing unit 4206 is configured to detect, by the movementdetection unit (e.g., movement detection unit 4220), a user movement ofthe electronic device 4200; and, in response to detecting the movement:enable display (e.g., with display enabling unit 4210), on the displayunit (e.g., display unit 4202), of an animated reveal of a clock face,wherein the animation comprises: enabling display (e.g., with displayenabling unit 4210), on the display unit (e.g., display unit 4202), ofan hour hand and a minute hand; and enabling display (e.g., with displayenabling unit 4210), on the display unit (e.g., display unit 4202), of afirst hour indication; and after displaying the first hour indication,enabling display (e.g., with display enabling unit 4210), on the displayunit (e.g., display unit 4202), of a second hour indication, wherein thesecond hour indication is displayed on the clock face at a positionafter the first hour indication in a clockwise direction.

In some embodiments, the processing unit 4206 is further configured to:after enabling display (e.g., with display enabling unit 4210), on thedisplay unit (e.g., display unit 4202), of the second hour indication,enable display (e.g., with display enabling unit 4210), on the displayunit (e.g., display unit 4202), of a first minute indication; and enabledisplay (e.g., with display enabling unit 4210), on the display unit(e.g., display unit 4202), of a second minute indication, wherein thesecond minute indication is displayed on the clock face at a positionafter the first minute indication in a clockwise direction. In someembodiments, the hour hand and the minute hand are displayed before thefirst hour indication. In some embodiments, the processing unit 4206 isfurther configured to: enable display (e.g., with display enabling unit4210), on the display unit (e.g., display unit 4202), of an animatedreveal of an outline of the clock face, wherein the outline of the clockface is animated to be displayed progressively in a clockwise direction.In some embodiments, after the animation, the clock face indicates acurrent time. In some embodiments, the processing unit 4206 is furtherconfigured to: enable display (e.g., with display enabling unit 4210),on the display unit (e.g., display unit 4202), of an affordance as acomplication on the clock face, wherein the affordance represents anapplication; detect (e.g., with detecting unit 4208) a contact on theaffordance on the touch-sensitive surface unit touch-sensitive surfaceunit 4204), and in response to detecting the contact: launch (e.g., withlaunching unit 4212) the application represented by the affordance. Insome embodiments, the processing unit 4206 is further configured to:enable update (e.g., with update enabling unit 4214), on the displayunit (e.g., display unit 4202), of a color of the clock face, whereinupdating the color comprises continuously changing the color of theclock face over time. In some embodiments, the color of the clock faceis a background color of the clock face. In some embodiments, the clockface comprises a seconds hand, and the color of the clock face is acolor of a seconds hand. In some embodiments, the processing unit 4206is further configured to: detect (e.g., with detecting unit 4208), bythe movement detection unit (e.g., movement detection unit 4220), asecond user movement of the electronic device 4200; and, in response todetecting the second movement: enable display (e.g., with displayenabling unit 4210), on the display unit (e.g., display unit 4202), of asecond color of the clock face, wherein the second color is differentfrom the first color; and enable update (e.g., with update enabling unit4214), on the display unit (e.g., display unit 4202), of the secondcolor of the clock face, wherein updating the second color comprisescontinuously changing the second color of the clock face over time. Insome embodiments, the processing unit 4206 is further configured to:receive (e.g., with receiving unit 4216) data representing a name; andin response to receiving the data: generate (e.g., with generating unit4218) a monogram; and enable display (e.g., with display enabling unit4210), on the display unit (e.g., display unit 4202), of the monogram asa second affordance on the clock face.

The operations described above with reference to FIG. 27A are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.42. For example, detecting operation 2702 and displaying operation 2704may be implemented by event sorter 170, event recognizer 180, and eventhandler 190. Event monitor 171 in event sorter 170 detects a contact ontouch-sensitive display 112, and event dispatcher module 174 deliversthe event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface corresponds to apredefined event or sub event, such as activation of an affordance on auser interface. When a respective predefined event or sub-event isdetected, event recognizer 180 activates an event handler 190 associatedwith the detection of the event or sub-event. Event handler 190 mayutilize or call data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 43 shows an exemplaryfunctional block diagram of an electronic device 4300 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 4300 are configured to perform the techniques described above.The functional blocks of the device 4300 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 43 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 43, an electronic device 4300 includes a display unit4302 configured to display a graphic user interface, optionally, atouch-sensitive surface unit 4304 configured to receive contacts, and aprocessing unit 4306 coupled to the display unit 4302, and optionally,the touch-sensitive surface unit 4304. In some embodiments, theprocessing unit 4306 includes a detecting unit 4308, a display enablingunit 4310, a launching unit 4312, and an updating unit 4314.

The processing unit 4306 is configured to enable display (e.g., withdisplay enabling unit), on the display unit (e.g., display unit 4302),of a user interface screen, the user interface screen including: a clockface; and an affordance, wherein the affordance represents anapplication, wherein the affordance comprises a set of informationobtained from the application, wherein the set of information is updated(e.g., with updating unit 4314) in accordance with data from theapplication, and wherein the affordance is displayed as a complicationon the clock face; detect (e.g., with detecting unit 4308) a contact onthe displayed affordance on the touch-sensitive surface unit (e.g.,touch-sensitive surface 4304), and in response to detecting the contact:launch (e.g., with launching unit 4312) the application represented bythe affordance.

The operations described above with reference to FIG. 32 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.43. For example, displaying operation 3202, detecting operation 3204,and launching operation 3206 may be implemented by event sorter 170,event recognizer 180, and event handler 190. Event monitor 171 in eventsorter 170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

In accordance with some embodiments, FIG. 44 shows an exemplaryfunctional block diagram of an electronic device 4400 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 4400 are configured to perform the techniques described above.The functional blocks of the device 4400 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 44 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 44, an electronic device 4400 includes a display unit4402 configured to display a graphic user interface, optionally, atouch-sensitive surface unit 4404 configured to receive contacts and todetect intensity of contacts, optionally, a rotatable input unit 4442configured to receive rotatable input (e.g., from a rotatable inputmechanism), optionally, a rotatable and depressible input unit 4444configured to receive rotatable and depressible input (e.g., from arotatable and depressible input mechanism), and a processing unit 4206coupled to the display unit 4202, optionally, the touch-sensitivesurface unit 4204, optionally, the rotatable input unit 4442, andoptionally, the rotatable and depressible input unit 4444. In someembodiments, the processing unit 4406 includes a detecting unit 4408, adisplay enabling unit 4410, a determining unit 4412, an entering unit4414, a visual distinguishment enabling unit 4416, a visual indicationenabling unit 4418, a launching unit 4420, an animation enabling unit4422, a changing unit 4424, an editing unit 4426, an obtaining unit4428, a removal enabling unit 4430, a translation enabling unit 4432, anexiting unit 4438, a reduction enabling unit 4434, an increase enablingunit 4436, a selecting unit 4440, an update enabling unit 4446, and areceiving unit 4448.

The processing unit 4406 is configured to enable display (e.g., withdisplay enabling unit 4410), on the display unit (e.g., 4402), of a userinterface screen including a clock face; detect (e.g., with detectingunit 4408) a contact on the touch-sensitive surface unit (e.g., 4404),the contact having a characteristic intensity, and in response todetecting the contact: determine (e.g., with determining unit 4412)whether the characteristic intensity is above an intensity threshold;and in accordance with a determination that the characteristic intensityis above the intensity threshold: enter (e.g., with entering unit 4414)a clock face edit mode of the electronic device; enable visualdistinguishment (e.g., with visual distinguishment enabling unit 4416,on the display unit (e.g., display unit 4402), of the displayed clockface to indicate the clock face edit mode; and detect (e.g., withdetecting unit 4408) a second contact on the touch-sensitive surfaceunit, wherein the second contact is on the visually distinguisheddisplayed clock face, and in response to detecting the second contact:enable visual indication (e.g., with visual indication enabling unit4418), on the display unit (e.g., display unit 4402), of an element ofthe clock face for editing.

In some embodiments, the clock face includes an affordance representingan application, wherein the contact is on the affordance representingthe application on the touch-sensitive surface unit, and wherein theprocessing unit 4406 is further configured to: in accordance with adetermination that the characteristic intensity is not above theintensity threshold: launch (e.g., with launching unit 4420) theapplication represented by the affordance. In some embodiments, enablingvisual distinguishment (e.g., with visual distinguishment enabling unit4416), on the display unit (e.g., display unit 4402), of the displayedclock face comprises reducing size of the displayed clock face. In someembodiments, enabling visual indication (e.g., with visual indicationenabling unit 4418), on the display unit (e.g., display unit 4402), ofthe element of the clock face for editing comprises: enabling visualdistinguishment enabling unit 4416), on the display unit (e.g., displayunit 4402), of an outline around the element of the clock face. In someembodiments, the processing unit 4406 is further configured to: enableanimation (e.g., with animation enabling unit 4422), on the display unit(e.g., 4402), of the outline around the element of the clock face todepict a rhythmic expansion and contraction of the outline. In someembodiments, visually indicating the element of the clock face forediting comprises: enabling animation (e.g., with animation enablingunit 4422), on the display unit (e.g., 4402), of the element of theclock face to depict a rhythmic expansion and contraction of the elementof the clock face. In some embodiments, visually indicating the elementof the clock face for editing comprises: enabling animation (e.g., withanimation enabling unit 4422), on the display unit (e.g., 4402), of theelement of the clock face to depict a flashing of the element of theclock face. In some embodiments, the processing unit 4406 is furtherconfigured to enable change (e.g., with changing unit 4424), on thedisplay unit (e.g., 4402), of a color of the element of the clock face,and wherein visually indicating the element of the clock face forediting comprises: changing the color of the element of the clock face.In some embodiments, the electronic device further comprises a rotatableinput unit (e.g., rotatable input unit 4442), wherein the processingunit 4406 is coupled to the rotatable input unit, and wherein theprocessing unit 4406 is further configured to: after entering the clockface edit mode: detect (e.g., with detecting unit 4408) a movementcorresponding to a rotatable input from the rotatable input unit (e.g.,rotatable input unit 4442), and in response to detecting the movement:edit (e.g., with editing unit 4426) an aspect of the visually indicatedelement of the clock face. In some embodiments, the processing unit 4406is further configured to enable change (e.g., with changing unit 4424),on the display unit (e.g., 4402), of a color of the visually indicatedelement of the clock face, and wherein editing the aspect of thevisually indicated element of the clock face comprises: enabling change(e.g., with changing unit 4424), on the display unit (e.g., display unit4402), of the color of the visually indicated element of the clock face.In some embodiments, the processing unit 4406 is further configured toenable change (e.g., with changing unit 4424), on the display unit(e.g., 4402), of a color of the visually indicated element of the clockface, wherein the visually indicated element of the clock face is aclock face background, and wherein editing (e.g., with editing unit4426) the aspect of the visually indicated element of the clock facecomprises: enabling change (e.g., with changing unit 4424), on thedisplay unit (e.g., display unit 4402), of a color of the clock facebackground. In some embodiments, the processing unit 4406 is furtherconfigured to enable change (e.g., with changing unit 4424), on thedisplay unit (e.g., 4402), of a color of the visually indicated elementof the clock face, wherein the clock face comprises a seconds hand, andwherein editing (e.g., with editing unit 4426) the aspect of thevisually indicated element of the clock face comprises: enabling change(e.g., with changing unit 4424), on the display unit (e.g., display unit4402) of a color of the seconds hand. In some embodiments, the clockface comprises an affordance representing an application, wherein theaffordance is displayed, on the display unit (e.g., display unit 4402),as a complication on the clock face, wherein the affordance indicates afirst set of information obtained from the application, and whereinediting (e.g., with changing unit 4424) the aspect of the visuallyindicated element of the clock face comprises enabling update (e.g.,with updating unit 4446), on the display unit (e.g., display unit 4402),of the affordance to indicate a second set of information obtained fromthe application. In some embodiments, the clock face comprises anaffordance representing an application, wherein the affordance isdisplayed as a complication on the clock face on the display unit,wherein the affordance indicates a set of information obtained from afirst application, wherein editing the aspect of the visually indicatedelement of the clock face comprises enabling update (e.g., with updatingunit 4446), on the display unit (e.g., display unit 4402), of theaffordance to indicate a set of information obtained from a secondapplication, and wherein the first and the second applications aredifferent. In some embodiments, the clock face comprises a plurality ofvisible divisions of time, wherein the plurality comprises a firstnumber of visible divisions of time, and wherein editing the aspect ofthe visually indicated element of the clock face comprises enablingchange (e.g., with changing unit 4424), on the display unit, of thefirst number of visible divisions of time in the plurality to a secondnumber of visible divisions of time in the plurality. In someembodiments, the second number is greater than the first number. In someembodiments, the second number is less than the first number. In someembodiments, the processing unit 4406 is further configured to: afterentering the clock face edit mode: enable display (e.g., with displayenabling unit 4410), on the display unit (e.g., 4402), of an indicatorof position along a series of positions, the indicator indicating afirst position along the series; and in response to receiving the dataindicating the rotatable input of the rotatable input unit (e.g.,rotatable input unit 4442): enable update (e.g., with update enablingunit 4446), on the display unit (e.g., display unit 4402), of theindicator of position to indicate a second position along the series. Insome embodiments, the indicator of position along a series of positionsindicates a position of a currently selected option for the editableaspect along a series of selectable options for the editable aspect ofthe visually indicated element of the clock face. In some embodiments,the indicator is displayed on the display at a position adjacent to therotatable input unit. In some embodiments, the editable aspect of thevisually indicated element of the clock face is color, and wherein theindicator comprises a series of colors, wherein each position in theseries depicts a color, and wherein the color of the currently indicatedposition along the series is representative of the color of the visuallyindicated element. In some embodiments, the processing unit 4406 isfurther configured to: after visually indicating the element of theclock face for editing: detect (e.g., with detecting unit 4408) a thirdcontact on the touch-sensitive surface unit (e.g., touch-sensitivesurface unit 4404) at a second displayed element of the clock face, andin response to detecting the third contact: enable removal (e.g., withremoval enabling unit 4430), on the display unit (e.g., display unit4402), of the visual indication of the first element of the clock facefor editing; and enable visual indication (e.g., with visual indicationenabling unit 4418), on the display unit (e.g., display unit 4402), ofthe second element of the clock face for editing. In some embodiments,before detecting the third contact, the indicated first element of theclock face is indicated by an outline around the element, whereinenabling removal (e.g., with removal enabling unit 4430) of the visualindication of the first element comprises: enabling translation (e.g.,with translation enabling unit 4432), on the display unit (e.g., displayunit 4402), of the outline on-screen away from the first element. Insome embodiments, enabling visual indication (e.g., with visualindication enabling unit 4418), on the display unit (e.g., display unit4402), of the second element of the clock face for editing comprises:enabling translation (e.g., with translation enabling unit 4432), on thedisplay unit (e.g., display unit 4402), of a visible outline on-screentowards from the second element; and enabling display (e.g., withdisplay enabling unit 4410), on the display unit (e.g., 4402), of thevisible outline around the second element, wherein the translating andthe displaying comprise a continuous on-screen movement of the visibleoutline. In some embodiments, the processing unit 4406 is furtherconfigured to: after enabling visual indication (e.g., with visualindication enabling unit 4418), on the display (e.g., display unit4402), of the first element of the clock face for editing, detect aswipe on the touch-sensitive surface unit, and in response to detectingthe swipe: enable removal (e.g., with removal enabling unit 4430), onthe display unit (e.g., display unit 4402), of the visual indication ofthe first element of the clock face for editing; enable visualindication (e.g., with visual indication enabling unit 4418), on thedisplay unit (e.g., display unit 4402), of a second element of the clockface for editing; after visually indicating the second element of theclock face for editing, detect a user input, and in response todetecting the user input: edit (e.g., with editing unit 4426) a secondaspect of the visually indicated second element of the clock face,wherein the second aspect of the second element is different from thefirst aspect of the first element of the clock face. In someembodiments, the processing unit 4406 is further configured to: enabledisplay (e.g., with display enabling unit 4410), on the display unit(e.g., 4402), of a paging affordance on the user interface screen,wherein the paging affordance indicates an editable aspect of thecurrently indicated element of the clock face, a position of theeditable aspect of the currently indicated element within a sequence ofeditable aspects, and a total number of editable aspects within thesequence of editable aspects. In some embodiments, the processing unit4406 is further configured to: after entering the clock face edit modeof the electronic device: detect (e.g., with detecting unit 4408) afourth contact on the touch-sensitive surface unit (e.g.,touch-sensitive surface unit 4404), the fourth contact having a secondcharacteristic intensity, and in response to detecting the fourthcontact; determine (e.g., with determining unit 4412) whether the secondcharacteristic intensity is above a second intensity threshold; and inaccordance with a determination that the second characteristic intensityis above the second intensity threshold: exit (e.g., with exiting unit4438) the clock face edit mode; and enable cessation, on the displayunit (e.g., display unit 4402), of the visual distinguishment (e.g.,enabling the cessation of the visual distinguishment with visualdistinguishment unit 4416), on the display unit (e.g., display unit4402), of the displayed clock face. In some embodiments, enabling visualdistinguishment (e.g., with visual distinguishment unit 4416), on thedisplay unit (e.g., display unit 4402), of the displayed clock face toindicate the clock face edit mode further comprises reducing a size ofthe displayed clock face, and wherein enabling cessation, on the displayunit, of the visual distinguishment of the displayed clock facecomprises enabling an increase (e.g., with increase enabling unit 4436),on the display unit (e.g., display unit 4402), of the size of thedisplayed clock face. In some embodiments, the electronic device furthercomprises a rotatable and depressible input unit (e.g., rotatable anddepressible input unit 4444), wherein the processing unit 4406 iscoupled to the rotatable and depressible input unit, and wherein theprocessing unit 4406 is further configured to: after entering the clockface edit mode of the electronic device: detect (e.g., with detectingunit 4408) a depression corresponding to a rotatable and depressibleinput from the rotatable and depressible input unit (e.g., rotatable anddepressible input unit 4444), and in response to detecting thedepression: exit (e.g., with exiting unit 4438) the clock face editmode; and enable cessation, on the display unit, of the visualdistinguishment (e.g., enabling the cessation of the visualdistinguishment with visual distinguishment unit 4416), on the displayunit (e.g., display unit 4402), of the displayed clock face. In someembodiments, enabling visual distinguishment, on the display unit, ofthe displayed clock face to indicate the clock face edit mode comprises:enabling a reduction (e.g., with reduction enabling unit 4434), on thedisplay unit (e.g., display unit 4402), of a size of the displayed clockface, and wherein enabling cessation, on the display unit, of the visualdistinguishment (e.g., enabling the cessation of the visualdistinguishment with visual distinguishment unit 4416), on the displayunit (e.g., display unit 4402), of the displayed clock face comprises:enabling an increase (e.g., with increase enabling unit 4436), on thedisplay unit (e.g., display unit 4402), of the size of the displayedclock face. In some embodiments, the processing unit 4406 is furtherconfigured to: receive (e.g., with receiving unit 4448) a user input,and in response to receiving the user input: enter (e.g., with enteringunit 4414) a color selection mode of the electronic device 4400; whilein the color selection mode of the electronic device 4400, receive(e.g., with receiving unit 4448) data representing an image, and inresponse to receiving the data: select (e.g., with selecting unit 4440)a color of the image; and enable update (e.g., with update enabling unit4446), on the display unit (e.g., display unit 4402), of the displayedclock face, wherein enabling update the displayed clock face comprisesenabling change (e.g., with changing unit 4424), on the display unit(e.g., 4402), of a color of the clock face to the color of the image. Insome embodiments, selecting the color of the image comprises selecting acolor with greatest prevalence in the image.

The operations described above with reference to FIG. 28 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.44. For example, displaying operation 2802, detecting operation 2804,and determining operation 2806 may be implemented by event sorter 170,event recognizer 180, and event handler 190. Event monitor 171 in eventsorter 170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

In accordance with some embodiments, FIG. 45 shows an exemplaryfunctional block diagram of an electronic device 4500 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 4500 are configured to perform the techniques described above.The functional blocks of the device 4500 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 45 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 45, an electronic device 4500 includes a display unit4502 configured to display a graphic user interface, optionally, atouch-sensitive surface unit 4504 configured to receive contacts and todetect intensity of contacts, optionally, a rotatable input unit 4534configured to receive rotatable input (e.g., from a rotatable inputmechanism), and a processing unit 4506 coupled to the display unit 4502,optionally, the touch-sensitive surface unit 4504, and, optionally, therotatable input unit 4534. In some embodiments, the processing unit 4506includes a detecting unit 4508, a display enabling unit 4510, adetermining unit 4512, an entering unit 4514, a visual distinguishmentenabling unit 4516, a centering enabling unit 4518, a launching unit4520, a reduction enabling unit 4522, a translation enabling unit 4524,a simulation enabling unit 4526, an exiting unit 4528, a generating unit4530, an animation enabling unit 4532, an update enabling unit 4536, anda replacement enabling unit 4538.

The processing unit 4506 is configured to enable display, on the displayunit, on the touch-sensitive surface unit (e.g., touch-sensitive surfaceunit 4504) a user interface screen including a clock face; enabledisplay (e.g., with display enabling unit 4510), on the display unit(e.g., display unit 4502), on the touch-sensitive surface unit (e.g.,touch-sensitive surface unit 4504) a user interface screen including aclock face; detect a contact on the touch-sensitive surface unit (e.g.,touch-sensitive surface unit 4504), the contact having a characteristicintensity, and in response to detecting the contact: determine (e.g.,with determining unit 4512) whether the characteristic intensity isabove an intensity threshold; and in accordance with a determinationthat the characteristic intensity is above the intensity threshold:enter (e.g., with entering unit 4514) a clock face selection mode of theelectronic device; enable visual distinguishment (e.g, with visualdistinguishment enabling unit 4516), on the display unit (e.g., displayunit 4502), of the displayed clock face to indicate the clock faceselection mode, wherein the displayed clock face is centered on thedisplay; and detect (e.g., with detecting unit 4508) a swipe on thetouch-sensitive surface unit (e.g., touch-sensitive surface unit 4504),and in response to detecting the swipe: enable centering (e.g., withcentering enabling unit 4518), on the display unit (e.g., display unit4502), of a second clock face.

In some embodiments, the clock face includes an affordance representingan application, wherein the contact is on the affordance representingthe application on the touch-sensitive surface unit (e.g.,touch-sensitive surface unit 4504), and the processing unit is furtherconfigured to: in accordance with a determination that thecharacteristic intensity is not above the intensity threshold: launch(e.g., with launching unit 4520) the application represented by theaffordance. In some embodiments, visually distinguishing the displayedclock face to indicate the clock face selection mode comprises enablingreduction (e.g., with reduction enabling unit 4522), on the display unit(e.g., display unit 4502), of the size of the displayed clock face. Insome embodiments, the first and the second clock faces are among aplurality of clock faces, the plurality including at least the first andthe second clock face. In some embodiments, entering the clock faceselection mode of the electronic device further comprises: enablingdisplay (e.g., with display enabling unit 4510), on the display unit(e.g., display unit 4502), of at least the first and the second clockfaces from the plurality of clock faces, wherein the displayed clockfaces are shown at a reduced size and arranged in a sequence of clockfaces, and wherein the clock faces in the sequence that are notcurrently centered are displayed in a partial view. In some embodiments,the second clock face is arranged after the first clock face in thesequence of clock faces, wherein enabling centering (e.g., withcentering enabling unit 4518), on the display unit (e.g., display unit4502), of the second clock face comprises: enabling translation (e.g.,with translation enabling unit 4524), on the display unit (e.g., displayunit 4502), of the first clock face on-screen; and enabling display(e.g., with display enabling unit 4510), on the display unit (e.g.,display unit 4502), of a partial view of the first clock face. In someembodiments, centering the second clock face on the display comprises:enabling translation (e.g., with translation enabling unit 4524), on thedisplay unit (e.g., display unit 4502), of the second clock face ontothe displayed user interface screen; and enabling translation (e.g.,with translation enabling unit 4524), on the display unit (e.g., displayunit 4502), of the first clock face off of the displayed user interfacescreen. In some embodiments, enabling centering (e.g., with centeringenabling unit 4518), on the display unit (e.g., display unit 4502), ofthe second clock face on the display comprises enabling simulation(e.g., with simulation enabling unit 4526), on the display unit (e.g.,display unit 4502), of a movement of the second clock face towards theuser on the display. In some embodiments, the processing unit is furtherconfigured to: after centering the second clock face on the display:detect (e.g., with detecting unit 4508) a contact on the displayedsecond clock face on the touch-sensitive surface unit (e.g.,touch-sensitive surface unit 4504), and in response to detecting thecontact: exit (e.g., with exiting unit 4528) the clock face selectionmode; and enable display (e.g., with display enabling unit 4510), on thedisplay unit (e.g., display unit 4502), of a second user interfacescreen including the second clock face. In some embodiments, theprocessing unit is further configured to: after entering the clock faceselection mode: detect (e.g., with detecting unit 4508) a second swipeon the touch-sensitive surface unit (e.g., touch-sensitive surface unit4504), and in response to detecting the second swipe: enable centering(e.g., with centering enabling unit 4518), on the display unit (e.g.,display unit 4502), of a clock face generation affordance on thedisplay; detect (e.g., with detecting unit 4508) a contact on thedisplayed clock face generation affordance, and in response to detectingthe contact: generate (e.g., with generating unit 4530) a third clockface; and enable display (e.g., with display enabling unit 4510), on thedisplay unit (e.g., display unit 4502), of the third clock face, whereinthe third clock face is centered on the display. In some embodiments,the processing unit is further configured to: after entering the clockface selection mode, and before detecting the second swipe: enabledisplay (e.g., with display enabling unit 4510), on the display unit(e.g., display unit 4502), of at least a partial view of the clock facegeneration affordance on the user interface screen. In some embodiments,the processing unit is further configured to: after entering the clockface selection mode: detect (e.g., with detecting unit 4508) a thirdswipe on the touch-sensitive surface unit (e.g., touch-sensitive surfaceunit 4504), and in response to detecting the third swipe: enablecentering (e.g., with centering enabling unit 4518), on the display unit(e.g., display unit 4502), of a random clock face generation affordanceon the display; detect (e.g., with detecting unit 4508) a contact on thedisplayed random clock face generation affordance on the touch-sensitivesurface unit (e.g., touch-sensitive surface unit 4504), and in responseto detecting the contact: generate (e.g., with generating unit 4530) afourth clock face, wherein the fourth clock face is randomly generated;and enable display (e.g., with display enabling unit 4510), on thedisplay unit (e.g., display unit 4502), of the fourth clock face,wherein the fourth clock face is centered on the display. In someembodiments, the fourth clock face is different from the first clockface, the second clock face, and the third clock face. In someembodiments, the processing unit is further configured to: afterentering the clock face selection mode, and before detecting the thirdswipe: enable display (e.g., with display enabling unit 4510), on thedisplay unit (e.g., display unit 4502), of at least a partial view ofthe random clock face generation affordance on the user interfacescreen. In some embodiments, enabling centering (e.g., with centeringenabling unit 4518), on the display unit (e.g., display unit 4502), ofthe first clock face, the second clock face, the third clock face, orthe fourth clock face further comprises: enabling visibledistinguishment (e.g., with visual distinguishment enabling unit 4516),on the display unit (e.g., display unit 4502) of an outline around thecentered clock face. In some embodiments, the processing unit is furtherconfigured to: enable animation (e.g., with animation enabling unit4532), on the display unit (e.g., display unit 4502), of the outlinearound the centered clock face to depict a rhythmic expansion andcontraction of the outline. In some embodiments, enabling centering(e.g., with centering enabling unit 4518), on the display unit (e.g.,display unit 4502), of the first clock face, the second clock face, thethird clock face, or the fourth clock face further comprises: enablinganimation (e.g., with animation enabling unit 4532), on the display unit(e.g., display unit 4502), of the centered clock face to depict arhythmic expansion and contraction of the centered clock face. In someembodiments, enabling centering (e.g., with centering enabling unit4518), on the display unit (e.g., display unit 4502), of the first clockface, the second clock face, the third clock face, or the fourth clockface further comprises: enabling animation (e.g., with animationenabling unit 4532), on the display unit (e.g., display unit 4502), ofthe centered clock face to depict a flashing of the centered clock face.In some embodiments, the first clock face, the second clock face, thethird clock face, or the fourth clock face is centered on the displayunit (e.g., display unit 4502), the centered clock face comprises arepresentation of a first image, and the processing unit is furtherconfigured to: detect a contact (e.g., with detecting unit 4508) on thetouch-sensitive surface unit (e.g., touch-sensitive surface unit 4504)on the displayed representation, and in response to detecting thecontact on the displayed representation: enable display, on the displayunit (e.g., display unit 4502), of a second user interface screen, thesecond user interface screen comprising: a background based on the firstimage; a first user interface object indicating a date; and a seconduser interface object indicating a time of day. In some embodiments,device 4500 further comprises a rotatable input unit (e.g., rotatableinput unit 4534), the processing unit 4506 is coupled to the rotatableinput unit (e.g., rotatable input unit 4534), and the processing unit isfurther configured to: while enabling display, on the display unit(e.g., display unit 4502), of the second user interface screen, detect amovement (e.g., with detecting unit 4508) of the rotatable input unit(e.g., rotatable input unit 4534) corresponding to a rotatable inputfrom the rotatable and depressible input unit, wherein the movement isin a first direction of rotation, and in response to detecting themovement: enable display, on the display unit (e.g., display unit 4502),of a second image, wherein the second image is a cropped image based onthe first image. In some embodiments, the processing unit is furtherconfigured to: detect a second contact (e.g., with detecting unit 4508)on the touch-sensitive surface unit (e.g., touch-sensitive surface unit4504), the second contact having a second characteristic intensity, andin response to detecting the second contact: determine (e.g., withdetermining unit 4512) whether the second characteristic intensity isabove a second intensity threshold; and in accordance with adetermination that the second characteristic intensity is above thesecond intensity threshold: enable display (e.g., with display enablingunit 4510), on the display unit (e.g., display unit 4502), of a thirduser interface screen, the third user interface screen comprising: asecond background based on the second image; a third user interfaceobject indicating a date; and a fourth user interface object indicatinga time of day. In some embodiments, the processing unit is furtherconfigured to: in accordance with a determination that the secondcharacteristic intensity is not above the second intensity threshold:enable update (e.g., with update enabling unit 4536), on the displayunit (e.g., display unit 4502), of the second image, wherein the updatecomprises one or more of: translating the second image on the displayunit (e.g., display unit 4502); cropping the second image; or zoomingthe second image. In some embodiments, the processing unit is furtherconfigured to: while enabling display (e.g., with display enabling unit4510), on the display unit (e.g., display unit 4502), of the second userinterface screen, detect (e.g., with detecting unit 4508) a secondmovement of the rotatable input unit (e.g., rotatable input unit 4534)corresponding to a second rotatable input from the rotatable anddepressible input unit, wherein the second movement is in a seconddirection of rotation different from the first direction of rotation,and in response to detecting the second movement: enable replacement(e.g., with replacement enabling unit 4538), on the display unit (e.g.,display unit 4502), of the second user interface screen with a thirduser interface screen, the third user interface screen including two ormore images. In some embodiments, the processing unit is furtherconfigured to: enable display (e.g., with display enabling unit 4510),on the display unit (e.g., display unit 4502), of a paging affordance onthe user interface screen, wherein the paging affordance indicates thecurrently centered clock face, a position of the centered clock facewithin a sequence of clock faces, and a total number of clock faceswithin the sequence of clock faces.

The operations described above with reference to FIGS. 29-30 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.45. For example, displaying operation 2902, detecting operation 2904,and determining operation 2906 may be implemented by event sorter 170,event recognizer 180, and event handler 190. Event monitor 171 in eventsorter 170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

In accordance with some embodiments, FIG. 46 shows an exemplaryfunctional block diagram of an electronic device 4600 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 4600 are configured to perform the techniques described above.The functional blocks of the device 4600 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 46 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 46, an electronic device 4600 includes a display unit4602 configured to display a graphic user interface, optionally, atouch-sensitive surface unit 4604 configured to receive contacts,optionally, a rotatable input unit 4618 configured to receive rotatableinput (e.g., from a rotatable input mechanism), optionally, an audiounit 4620 configured to generate audio, optionally, a haptic unit 4622configured to generate haptic output, and a processing unit 4606 coupledto the display unit 4502, optionally, the touch-sensitive surface unit4504, optionally, the rotatable input unit 4618, optionally, the audiounit 4620, and optionally, the haptic unit 4622. In some embodiments,the processing unit 4606 includes a detecting unit 4608, a displayenabling unit 4610, an entering unit 4612, an update enabling unit 4614,and a setting unit 4616.

The processing unit 4606 is configured to enable display (e.g., withdisplay enabling unit 4610), on the display unit (e.g., display unit4602), of a user interface screen, the user interface screen including:a clock face; and an affordance on the clock face, the affordanceindicating a first time of day; detect (e.g., with detecting unit 4608)a contact on the touch-sensitive surface unit (e.g., touch-sensitivesurface unit 4604); and in response to detecting the contact: enter(e.g., with entering unit 4612) a user interaction mode of theelectronic device; while the electronic device is in the userinteraction mode, detect (e.g., with detecting unit 4608) a rotatableinput from the rotatable input unit (e.g., rotatable input unit 4618),and in response to detecting the rotatable input: enable update (e.g.,with update enabling unit 4614), on the display unit (e.g., display unit4602), of the affordance to indicate a second time of day; detect (e.g.,with detecting unit 4608) a second contact on the touch-sensitivesurface unit (e.g., touch-sensitive surface unit 4604) at the affordanceindicating the second time, and in response to detecting the secondcontact: set (e.g., with setting unit 4616) a user reminder for thesecond time of day.

In some embodiments, setting the user reminder for the second time ofday comprises: enabling display (e.g., with display enabling unit 4610),on the display unit (e.g., display unit 4602), of a second affordance onthe display, the second affordance representing a user prompt to set analert for the second time of day. In some embodiments, the processingunit is further configured to enable display (e.g., with displayenabling unit 4610), on the display unit (e.g., display unit 4602), of avisual alert for the second time of day, and wherein the user reminderfor the third time of day comprises the visual alert for the second timeof day. In some embodiments, the electronic device 4600 furthercomprises an audio unit (e.g., audio unit 4620), wherein the processingunit is coupled to the audio unit, and wherein the processing unit isfurther configured to enable an audio alert for the second time of dayvia the audio unit (e.g., with audio unit 4620), and wherein the userreminder for the third time of day comprises the audio alert for thesecond time of day. In some embodiments, the electronic device 4600further comprises a haptic unit (e.g., haptic unit 4622), wherein theprocessing unit is coupled to the haptic unit, and wherein theprocessing unit is further configured to enable a haptic alert for thesecond time of day via the haptic unit (e.g., with haptic unit 4622),and wherein the user reminder for the second time of day comprises thehaptic alert for the second time of day.

The operations described above with reference to FIG. 31 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.46. For example, displaying operation 3102, detecting operation 3104,and entering operation 3106 may be implemented by event sorter 170,event recognizer 180, and event handler 190. Event monitor 171 in eventsorter 170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

In accordance with some embodiments, FIG. 47 shows an exemplaryfunctional block diagram of an electronic device 4700 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 4700 are configured to perform the techniques described above.The functional blocks of the device 4700 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 47 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 47, an electronic device 4700 includes a display unit4702 configured to display a graphic user interface, optionally, atouch-sensitive surface unit 4704 configured to receive contacts,optionally, an audio unit 4738 configured to generate audio, optionally,a haptic unit 4740 configured to generate haptic output, optionally, alocation sensing unit 4742 configured to sense location, optionally, amovement detection unit 4744, and a processing unit 4706 coupled to thedisplay unit 4702, optionally, the touch-sensitive surface unit 4704,optionally, the audio unit 4738, optionally, the haptic unit 4740,optionally, the location sensing unit 4742, and optionally, the movementdetection unit 4744. In some embodiments, the processing unit 4706includes a detecting unit 4708, a display enabling unit 4710, asubstitution enabling unit 4712, an animation enabling unit 4714, areceiving enabling unit 4716, a determining unit 4718, a removalenabling unit 4720, a launching unit 4722, an accessing unit 4724, anobtaining unit 4726, an update enabling unit 4728, a moving enablingunit 4730, a starting unit 4732, a stopping unit 4734, and a providingunit 4736.

The processing unit 4706 is configured to enable display (e.g., withdisplay enabling unit 4710), on the display unit (e.g., display unit4702), of a user interface screen, the user interface screen including aplurality of affordances, the plurality including a first affordance,wherein the first affordance indicates a clock face that includes: anindication of time; and an outline; detect (e.g., with detecting unit4708) a contact on the displayed first affordance on the touch-sensitivesurface unit (e.g., touch-sensitive surface unit 4704); and in responseto detecting the contact: enable substitution (e.g., with substitutionenabling unit 4712), on the display unit (e.g., display unit 4702), ofthe user interface screen with a second user interface screen, whereinthe substitution comprises retaining one of the one or more of theindication of time and the outline, wherein the retained indication oftime or outline is displayed on the second user interface screen at asize larger than on the first user interface screen.

In some embodiments, the processing unit 4706 is further configured to:enable animation (e.g., with animation enabling unit 4714), on thedisplay unit (e.g., display unit 4702), of the one or more retainedelements by progressively displaying the element on the second userinterface screen. In some embodiments, the outline is retained, andwherein the outline is progressively displayed in a rotational motion.

In some embodiments, the processing unit 4706 is further configured to:receive (e.g., with receiving unit 4716) a notification; determine(e.g., with determining unit 4718) whether the notification has beenmissed; and in accordance with a determination that notification hasbeen missed: enable display (e.g., with display enabling unit 4710), onthe display unit (e.g., display unit 4702), of an affordance, theaffordance indicating a missed notification. In some embodiments, anaspect of the displayed affordance represents a number of missednotifications received by the electronic device. In some embodiments,the processing unit 4706 is further configured to: receive datarepresenting user viewing of the missed notification, and in response toreceiving the data: enable removal (e.g., with removal enabling unit4720), on the display unit (e.g., display unit 4702), of the affordance.In some embodiments, the processing unit 4706 is further configured to:enable display (e.g., with display enabling unit 4710), on the displayunit (e.g., display unit 4702), of a stopwatch progress affordance, thestopwatch progress affordance indicating a currently running stopwatchapplication, wherein the stopwatch progress affordance comprises arepresentation of a digital stopwatch, and wherein the representation ofthe digital stopwatch is continuously updated (e.g., with updateenabling unit 4728) to indicate a stopwatch time generated by thecurrently running stopwatch application; detect (e.g., with detectingunit 4708) a contact on the displayed stopwatch progress affordance, andin response to detecting the contact: launch (e.g., with launching unit4722) the stopwatch application. In some embodiments, the electronicdevice comprises a location sensing unit (e.g., location sensing unit4742), wherein the processing unit 4706 is coupled to the locationsensing unit, and the processing unit 4706 is further configured to:while a clock face is displayed on the display unit, detect (e.g., withdetecting unit 4708) a contact on the touch-sensitive surface unit(e.g., touch-sensitive surface unit 4704), and in response to detectingthe contact: access (e.g., with accessing unit 4724) data representing adesignated home location, the designated home location having anassociated home time zone; obtain (e.g., with obtaining unit 4726) acurrent time zone of the electronic device from the location sensor;determine (e.g., with determining unit 4718) whether the current timezone is different from the home time zone; and in response to adetermination that the current time zone is different from the home timezone: enable update (e.g., with update enabling unit 4728), on thedisplay unit (e.g., display unit 4702), of the displayed clock face toindicate a current time at the home time zone. In some embodiments, thedesignated home location is user-designated. In some embodiments, thedesignated home location is a location designated by the system based ondata representing one or more of: amount of time spent at the location;which times of day are spent at the location; and number of contactentries associated with the location stored on the electronic device. Insome embodiments, the electronic device 4700 further includes a movementdetection unit (e.g., movement detection unit 4744), the processing unit4706 is coupled to the movement detection unit, and the processing unit4706 is further configured to: enable display (e.g., with displayenabling unit 4710), on the display unit (e.g., display unit 4702), of aclock face on the display, the displayed clock face comprising aplurality of pixels; detect (e.g., with detecting unit 4708) a movementof the electronic device 4700 via the movement detection unit (e.g.,movement detection unit 4744); and in response to detecting themovement: enable moving (e.g., with moving enabling unit 4730), on thedisplay unit (e.g., display unit 4702), of the displayed clock face onthe display, wherein moving comprises modifying in appearance a subsetof pixels in the plurality. In some embodiments, the processing unit4706 is further configured to: enable display (e.g., with displayenabling unit 4710), on the display unit (e.g., display unit 4702), of atachymeter user interface object comprising a start/stop affordance;detect (e.g., with detecting unit 4708) a user input at a first time; inresponse to detecting the user input: start (e.g., with starting unit4732) a virtual tachymeter; detect (e.g., with detecting unit 4708) asecond user input at a second time, the second time separated from thefirst time by a tachymeter interval; in response to detecting the seconduser input: stop (e.g., with stopping unit 4734) the virtual tachymeter;and enable display (e.g., with display enabling unit 4710), on thedisplay unit (e.g., display unit 4702), of a time value based on anumber of units of time in a predetermined interval divided by thetachymeter interval. In some embodiments, the processing unit 4706 isfurther configured to: enable display (e.g., with display enabling unit4710), on the display unit (e.g., display unit 4702), of a telemeteruser interface object comprising a start/stop affordance; detect (e.g.,with detecting unit 4708) a user input at a first time; in response todetecting the user input: start (e.g., with starting unit 4732) avirtual telemeter; detect (e.g., with detecting unit 4708) a second userinput at a second time, the second time separated from the first time bya telemeter interval; in response to detecting the second contact: stop(e.g., with stopping unit 4734) the virtual telemeter; and enabledisplay (e.g., with display enabling unit 4710), on the display unit(e.g., display unit 4702), of a distance based on the telemeterinterval. In some embodiments, the processing unit 4706 is furtherconfigured to: enable display (e.g., with display enabling unit 4710),on the display unit (e.g., display unit 4702), of a repeated intervaltimer user interface; receive (e.g., with receiving unit 4716) datarepresenting a user-designated time interval; and in response toreceiving the data representing the user-designated time interval:provide (e.g., with providing unit 4736) a user alert, wherein the useralert is repeated at times based on the user-designated time interval.In some embodiments, the user alert comprises one or more of: a visualalert, enabled on the display unit (e.g., display unit 4702); an audioalert, wherein the electronic device further comprises an audio unit(e.g., audio unit 4738) coupled to the processing unit, and wherein theprocessing unit is further configured to enable an audio alert via theaudio unit (e.g., audio unit 4738); and a haptic alert, wherein theelectronic device further comprises a haptic unit (e.g., haptic unit4740) coupled to the processing unit, and wherein the processing unit isfurther configured to enable a haptic alert via the haptic unit (e.g.,haptic unit 4738).

The operations described above with reference to FIG. 33 are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.47. For example, displaying operation 3302, detecting operation 3304,and substituting operation 3306 may be implemented by event sorter 170,event recognizer 180, and event handler 190. Event monitor 171 in eventsorter 170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

In accordance with some embodiments, FIG. 48 shows an exemplaryfunctional block diagram of an electronic device 4800 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 4800 are configured to perform the techniques described above.The functional blocks of the device 4800 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 48 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 48, an electronic device 4800 includes a display unit4802 configured to display a graphic user interface, optionally, atouch-sensitive surface unit 4804 configured to receive contacts, and aprocessing unit 4806 coupled to the display unit 4802, and optionally,the touch-sensitive surface unit 4804. In some embodiments, theprocessing unit 4806 includes an update enabling unit 4808, a displayenabling unit 4810, and an indication enabling unit 4812.

The processing unit 4806 is configured to enable display (e.g., withdisplay enabling unit 4810), on the display unit (e.g., display unit4802), of a character user interface object, the character userinterface object comprising representations of a first limb and a secondlimb, wherein the processing unit 4806 is configured to enable thecharacter user interface object to indicate (e.g., with indicationenabling unit 4812), on the display unit (e.g., display unit 4802), afirst time by: enabling indication (e.g., with indication enabling unit4812), on the display unit (e.g., display unit 4802), of a first hourwith the first limb and a first minute with the second limb; and enableupdate (e.g., with update enabling unit 4808), on the display unit(e.g., display unit 4802), of the character user interface object toindicate a second time, wherein the processing unit is configured toenable the character user interface object to indicate (e.g., withindication enabling unit 4812), on the display unit (e.g., display unit4802), the second time by: enabling indication (e.g., with indicationenabling unit 4812), on the display unit (e.g., display unit 4802), of asecond hour with the second limb and a second minute with the firstlimb.

In some embodiments, enabling update (e.g., with update enabling unit4808), on the display unit (e.g., display unit 4802), of the characteruser interface object to indicate a second time comprises enabling anextension of the first limb and a retraction of the second limb on thedisplay unit.

The operations described above with reference to FIG. 27B are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.48. For example, displaying operation 2712, updating operation 2714, andthe optional updating operation within block 2714 may be implemented byevent sorter 170, event recognizer 180, and event handler 190. Eventmonitor 171 in event sorter 170 detects a contact on touch-sensitivedisplay 112, and event dispatcher module 174 delivers the eventinformation to application 136-1. A respective event recognizer 180 ofapplication 136-1 compares the event information to respective eventdefinitions 186, and determines whether a first contact at a firstlocation on the touch-sensitive surface corresponds to a predefinedevent or sub event, such as activation of an affordance on a userinterface. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 may utilize orcall data updater 176 or object updater 177 to update the applicationinternal state 192. In some embodiments, event handler 190 accesses arespective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 49 shows an exemplaryfunctional block diagram of an electronic device 4900 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 4900 are configured to perform the techniques described above.The functional blocks of the device 4900 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 49 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 49, an electronic device 4900 includes a display unit4902 configured to display a graphic user interface, optionally, atouch-sensitive surface unit 4904 configured to receive contacts, and aprocessing unit 4906 coupled to the display unit 4902, and optionally,the touch-sensitive surface unit 4904. In some embodiments, theprocessing unit 4906 includes an update enabling unit 4908, a displayenabling unit 4910, and a moving enabling unit 4912.

The processing unit 4806 is configured to enable display (e.g., withdisplay enabling unit 4910), on the display unit (e.g., display unit4902), of a character user interface object on the display, thecharacter user interface object comprising a representation of a limb,the limb including: a first endpoint of the limb having a firstposition, wherein the first endpoint of the limb is an axis of rotationfor the limb, and a second endpoint of the limb having a secondposition, wherein the position of the second endpoint of the limbindicates a first time value; and enable update (e.g., with updateenabling unit 4908), on the display unit (e.g., display unit 4902), ofthe character user interface object to indicate a second time value,wherein enabling update, on the display unit, of the character userinterface object comprises enabling moving (e.g., with moving enablingunit 4912), on the display unit (e.g., display unit 4902), of the firstendpoint of the limb to a third position, and moving the second endpointof the limb to a fourth position to indicate the second time value.

In some embodiments, the character user interface object furthercomprises a representation of a second limb, the second limb including:a first endpoint of the second limb having a first position, wherein thefirst endpoint of the second limb is an axis of rotation for the secondlimb, and a second endpoint of the second limb having a second position,wherein the position of the second endpoint of the second limb indicatesa third time value, and the processing unit is further configured to:enable update (e.g., with update enabling unit 4908), on the displayunit (e.g., display unit 4902), of the character user interface objectto indicate a fourth time value, wherein enabling update, on the displayunit, of the character user interface object to indicate the fourth timevalue comprises enabling moving (e.g., with moving enabling unit 4912),on the display unit (e.g., display unit 4902), of the first endpoint ofthe second limb to a third position, and enabling moving (e.g., withmoving enabling unit 4912), on the display unit (e.g., display unit4902), of the second endpoint of the second limb to a fourth position toindicate the fourth time value.

The operations described above with reference to FIG. 27C are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.49. For example, displaying operation 2722 and updating operation 2724may be implemented by event sorter 170, event recognizer 180, and eventhandler 190. Event monitor 171 in event sorter 170 detects a contact ontouch-sensitive display 112, and event dispatcher module 174 deliversthe event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface corresponds to apredefined event or sub event, such as activation of an affordance on auser interface. When a respective predefined event or sub-event isdetected, event recognizer 180 activates an event handler 190 associatedwith the detection of the event or sub-event. Event handler 190 mayutilize or call data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 50 shows an exemplaryfunctional block diagram of an electronic device 5000 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 5000 are configured to perform the techniques described above.The functional blocks of the device 5000 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 50 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 50, an electronic device 5000 includes a display unit5002 configured to display a graphic user interface, optionally, atouch-sensitive surface unit 5004 configured to receive contacts, and aprocessing unit 5006 coupled to the display unit 5002, and optionally,the touch-sensitive surface unit 5004. In some embodiments, theprocessing unit 5006 includes an update enabling unit 5008, a displayenabling unit 5010, an animation enabling unit 5012, a translationenabling unit 5014, a change enabling unit 5016, and a moving enablingunit 5018.

The processing unit 5006 is configured to enable display (e.g., withdisplay enabling unit 5010), on the display unit (e.g., display unit5002), of a character user interface object, the character userinterface object comprising a representation of a limb, the limbincluding a first segment of the limb and a second segment of the limb,wherein the first segment of the limb connects a first endpoint of thelimb to a joint of the limb, the first endpoint of the limb having afirst position, and wherein the second segment of the limb connects asecond endpoint of the limb to the joint of the limb, the secondendpoint of the limb having a second position, wherein the joint of thelimb is an axis of rotation for the second segment of the limb, andwherein the position of the second endpoint of the limb indicates afirst time value; and enable update (e.g., with update enabling unit5008), on the display unit (e.g., display unit 5002), of the characteruser interface object to indicate a second time value, wherein enablingupdate comprises enabling moving (e.g., with moving enabling unit 5018),on the display unit (e.g., display unit 5002), of the second endpoint ofthe limb along the axis of rotation for the second segment of the limbto a third position to indicate the second time.

In some embodiments, enabling update (e.g., with update enabling unit5008), on the display unit (e.g., display unit 5002), of the characteruser interface object further comprises enabling moving (e.g., withmoving enabling unit 5018), on the display unit (e.g., display unit5002), of the first endpoint. In some embodiments, the character userinterface object further comprises a representation of a second limb,the second limb including a first segment of the second limb and asecond segment of the second limb, wherein the first segment of thesecond limb connects a first endpoint of the second limb to a joint ofthe second limb, the first endpoint of the second limb having a firstposition, wherein the second segment of the second limb connects asecond endpoint of the second limb to the joint of the second limb, thesecond endpoint of the second limb having a second position, wherein thejoint of the second limb is an axis of rotation for the second segmentof the second limb, and wherein the position of the second endpoint ofthe second limb indicates a third time, and wherein the processing unit5006 is further configured to: enable update (e.g., with update enablingunit 5008), on the display unit (e.g., display unit 5002), of thecharacter user interface object to indicate a fourth time, whereinenabling update comprises enabling moving (e.g., with moving enablingunit 5018), on the display unit (e.g., display unit 5002), of the secondendpoint of the second limb along the axis of rotation for the secondsegment of the second limb to a third position to indicate the fourthtime value. In some embodiments, the first limb indicates an hour andthe second limb indicates a minute. In some embodiments, the first limbindicates a minute and the second limb indicates an hour. In someembodiments, enabling update (e.g., with update enabling unit 5008), onthe display unit (e.g., display unit 5002), of the character userinterface object to indicate the second time further comprises: enablinganimation (e.g., with animation enabling unit 5012), on the display unit(e.g., display unit 5002), of the character user interface object,wherein enabling animation, on the display unit, of the character userinterface object comprises a motion of the first endpoint on-screen. Insome embodiments, enabling update (e.g., with update enabling unit5008), on the display unit (e.g., display unit 5002), of the characteruser interface object further comprises: enabling animation (e.g., withanimation enabling unit 5012), on the display unit (e.g., display unit5002), of the character user interface object, wherein enablinganimation, on the display unit, of the character user interface objectcomprises a rotation of the second segment at the joint on-screen. Insome embodiments, the processing unit is further configured to: enabletranslation (e.g., with translation enabling unit 5014), on the displayunit (e.g., display unit 5002), of the character user interface objecton-screen towards a center of the display. In some embodiments, enablingtranslation (e.g., with translation enabling unit 5014), on the displayunit (e.g., display unit 5002), of the character user interface objectcomprises animating the character user interface object to representwalking. In some embodiments, the processing unit is further configuredto: enable change (e.g., with change enabling unit 5016), on the displayunit (e.g., display unit 5002), of a visual aspect of the display tohighlight the character user interface object. In some embodiments, theprocessing unit is further configured to: enable animation (e.g., withanimation enabling unit 5012), on the display unit (e.g., display unit5002), of the character user interface object in response to beinghighlighted. In some embodiments, the character user interface objectfurther comprises a representation of a foot. In some embodiments, theprocessing unit is further configured to: enable animation (e.g., withanimation enabling unit 5012), on the display unit (e.g., display unit5002), of the foot to indicate passage of time. In some embodiments, thefirst time and the second time are the same. In some embodiments, theprocessing unit is further configured to: enable display (e.g., withdisplay enabling unit 5010), on the display unit (e.g., display unit5002), of a numerical indication of a time value.

The operations described above with reference to FIG. 27D are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.50. For example, displaying operation 2732 and updating operation 2734may be implemented by event sorter 170, event recognizer 180, and eventhandler 190. Event monitor 171 in event sorter 170 detects a contact ontouch-sensitive display 112, and event dispatcher module 174 deliversthe event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface corresponds to apredefined event or sub event, such as activation of an affordance on auser interface. When a respective predefined event or sub-event isdetected, event recognizer 180 activates an event handler 190 associatedwith the detection of the event or sub-event. Event handler 190 mayutilize or call data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

In accordance with some embodiments, FIG. 51 shows an exemplaryfunctional block diagram of an electronic device 5100 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 5100 are configured to perform the techniques described above.The functional blocks of the device 5100 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 51 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 51, an electronic device 5100 includes a display unit5102 configured to display a graphic user interface, optionally, atouch-sensitive surface unit 5104 configured to receive contacts,optionally, a movement detection unit 5120 configured to detectmovement, and a processing unit 5106 coupled to the display unit 5102,optionally, the touch-sensitive surface unit 5104 and optionally, themovement detection unit 5120. In some embodiments, the processing unit5106 includes a receiving unit 5108, a display enabling unit 5110, adetermining unit 5112, an update enabling unit 5114, an animationenabling unit 5116, a detecting unit 5118, an animation enabling unit5122, and a change enabling unit 5124.

The processing unit 5106 is configured to enable display (e.g., withdisplay enabling unit 5110), on the display unit (e.g., display unit5102), of a character user interface object, wherein the character userinterface object indicates a current time; receive (e.g., with receivingunit 5108) first data indicative of an event; determine (e.g., withdetermining unit 5112) whether the event meets a condition; and inaccordance with the determination that the event meets the condition:enable update (e.g., with update enabling unit 5114), on the displayunit (e.g., display unit 5102), of the displayed character userinterface object by changing (e.g., with change enabling unit 5124) avisual aspect of the character user interface object.

In some embodiments, after enabling update (e.g., with update enablingunit 5114), on the display unit (e.g., display unit 5102), of thedisplayed character user interface object, the character user interfaceobject still indicates the current time. In some embodiments, afterenabling update (e.g., with update enabling unit 5114), on the displayunit (e.g., display unit 5102), of the displayed character userinterface object, the character user interface object no longerindicates the current time. In some embodiments, the first dataindicates a calendar event; the condition corresponds to a duration ofthe calendar event; and determining whether the event meets thecondition comprises determining whether the current time is within theduration of the calendar event. In some embodiments, the calendar eventis a birthday, and wherein enabling update (e.g., with update enablingunit 5114), on the display unit (e.g., display unit 5102), of thedisplayed character user interface object comprises enabling animation(e.g., with animation enabling unit 5122), on the display unit (e.g.,display unit 5102), of the character user interface object to display abirthday greeting. In some embodiments, the calendar event is a holiday,and wherein updating the displayed character user interface objectcomprises enabling change (e.g., with change enabling unit 5124), on thedisplay unit (e.g., display unit 5102), of a visual aspect of thecharacter user interface object to reflect the holiday. In someembodiments, the first data indicates a notification, and wherein theprocessing unit is further configured to: enable display (e.g., withdisplay enabling unit 5110), on the display unit (e.g., display unit5102), of the notification on the display; and enable animation (e.g.,with animation enabling unit 5122), on the display unit (e.g., displayunit 5102), of the character user interface object to react to thedisplayed notification. In some embodiments, the first data indicates atime of day; the condition corresponds to a nighttime portion of theday; determining whether the event meets the condition comprisesdetermining whether the time of day is within the nighttime portion ofthe day; and enabling update (e.g., with update enabling unit 5114), onthe display unit (e.g., display unit 5102), of the displayed characteruser interface object comprises enabling change (e.g., with changeenabling unit 5124), on the display unit (e.g., display unit 5102), ofthe visual aspect of the character user interface object to representnighttime. In some embodiments, the first data indicates the currenttime; the condition corresponds to an hour on the hour; determiningwhether the event meets the condition comprises determining whether thecurrent time is an hour on the hour; and enabling update (e.g., withupdate enabling unit 5114), on the display unit (e.g., display unit5102), of the displayed character user interface object comprisesenabling animation (e.g., with animation enabling unit 5122), on thedisplay unit (e.g., display unit 5102), of the character user interfaceobject to announce the hour on the hour for one or more hours. In someembodiments, the first data indicates current or forecasted weather; thecondition corresponds to one or more designated weather conditions;determining whether the event meets the condition comprises determiningwhether the current or forecasted weather is one of the one or moredesignated weather conditions; and enabling update (e.g., with updateenabling unit 5114), on the display unit (e.g., display unit 5102), ofthe displayed character user interface object comprises enabling change(e.g., with change enabling unit 5124), on the display unit (e.g.,display unit 5102), of the visual aspect of the character user interfaceobject to reflect the current or forecasted weather. In someembodiments, the first data indicates a second electronic device; thecondition corresponds to a threshold proximity to the first electronicdevice; determining whether the event meets the condition comprisesdetermining whether the second electronic device is within the thresholdproximity to the first electronic device; and enabling update (e.g.,with update enabling unit 5114), on the display unit (e.g., display unit5102), of the displayed character user interface object comprisesenabling animation (e.g., with animation enabling unit 5122), on thedisplay unit (e.g., display unit 5102), of the character user interfaceobject to react to the second electronic device. In some embodiments,the first data indicates user activity; the condition corresponds to athreshold interval after a previous user activity; determining whetherthe event meets the condition comprises determining whether the firstdata is received outside of the threshold interval after the previoususer activity; and enabling update (e.g., with update enabling unit5114), on the display unit (e.g., display unit 5102), of the displayedcharacter user interface object comprises enabling animation (e.g., withanimation enabling unit 5122), on the display unit (e.g., display unit5102), of the character user interface object to reflect inactivity. Insome embodiments, the first data indicates user activity; the conditioncorresponds to current user activity; determining whether the eventmeets the condition comprises determining whether the user activity iscurrent user activity; and updating the displayed character userinterface object comprises enabling animation (e.g., with animationenabling unit 5122), on the display unit (e.g., display unit 5102), ofthe character user interface object to represent exercise. In someembodiments, the first data indicates user movement of the device (e.g.,from movement detection unit 5120); the condition corresponds to athreshold interval after a previous user movement of the device;determining whether the event meets the condition comprises determiningwhether the first data is received outside of the threshold intervalafter the previous user movement of the device (e.g., from movementdetection unit 5120); and enabling update (e.g., with update enablingunit 5114), on the display unit (e.g., display unit 5102), of thedisplayed character user interface object comprises enabling animation(e.g., with animation enabling unit 5122), on the display unit (e.g.,display unit 5102), of the character user interface object to representfatigue. In some embodiments, the first data indicates user contact onthe touch-sensitive surface unit (e.g., touch-sensitive surface unit5104); the condition corresponds to a user contact on the displayedcharacter user interface object; determining whether the event meets thecondition comprises determining whether the user contact on thetouch-sensitive surface unit is on the displayed character userinterface object; and enabling update (e.g., with update enabling unit5114), on the display unit (e.g., display unit 5102), of the displayedcharacter user interface object comprises enabling animation (e.g., withanimation enabling unit 5122), on the display unit (e.g., display unit5102), of the character user interface object to react to the contact.In some embodiments, the processing unit 5106 is further configured to:detect (e.g., with detecting unit 5118) a user input; and in response todetecting the user input, enable display (e.g., with display enablingunit 5110), on the display unit (e.g., display unit 5102), of thecharacter user interface object. In some embodiments, the user inputcomprises a user movement of the device, wherein the electronic devicefurther comprises a movement detection unit (e.g., movement detectionunit 5120), wherein the processing unit 5106 is coupled to the movementdetection unit, and wherein the processing unit 5106 is furtherconfigured to: detect, by the movement detection unit (e.g., movementdetection unit 5120), the user movement of the device 5100. In someembodiments, the user input comprises a contact on the touch-sensitivesurface unit (e.g., touch-sensitive surface unit 5104), and wherein theprocessing unit 5106 is further configured to detect (e.g., withdetecting unit 5118) the contact on the touch-sensitive surface unit.

The operations described above with reference to FIG. 27E are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.51. For example, displaying operation 2742, receiving operation 2744,and determining operation 2746 may be implemented by event sorter 170,event recognizer 180, and event handler 190. Event monitor 171 in eventsorter 170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

In accordance with some embodiments, FIG. 52 shows an exemplaryfunctional block diagram of an electronic device 5200 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 5200 are configured to perform the techniques described above.The functional blocks of the device 5200 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 52 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 52, an electronic device 5200 includes a display unit5202 configured to display a graphic user interface, optionally, atouch-sensitive surface unit 5204 configured to receive contacts,optionally, a movement detection unit 5216 configured to detectmovement, optionally, a button input unit 5218 configured to receiveinput from a button, and a processing unit 5206 coupled to the displayunit 5202, optionally, the touch-sensitive surface unit 5204,optionally, the movement detection unit 5216, and optionally, the buttoninput unit 5218. In some embodiments, the processing unit 5206 includesa setting unit 5208, a display enabling unit 5210, an animation enablingunit 5212, and a receiving unit 5214.

The processing unit 5206 is configured to set (e.g., with setting unit5208) the display unit (e.g., display unit 5202) to an inactive state;receive (e.g., with receiving unit 5214) first data indicative of anevent; in response to receiving the first data: set (e.g., with settingunit 5208) the display unit (e.g., display unit 5202) to an activestate; enable display (e.g., with display enabling unit 5210), on thedisplay unit (e.g., display unit 5202), of a character user interfaceobject on a side of the display; enable animation (e.g., with animationenabling unit 5212), on the display unit (e.g., display unit 5202), ofthe character user interface object towards a center of the display; andenable display (e.g., with display enabling unit 5210), on the displayunit (e.g., display unit 5202), of the character user interface objectat the center of the display in a position that indicates a currenttime.

In some embodiments, enabling animation (e.g., with animation enablingunit 5212), on the display unit (e.g., display unit 5202), of thecharacter user interface object provides the impression of walking. Insome embodiments, the electronic device 5200 includes a movementdetection unit (e.g., movement detection unit 5216), wherein themovement detection unit is coupled to the processing unit 5206, and theprocessing unit 5206 is further configured to receive (e.g., withreceiving unit 5214) input from the movement detection unit, and whereinthe event includes a motion raising the electronic device 5200 into aviewing position. In some embodiments, the electronic device 5200includes a button input unit (e.g., button input unit 5218), wherein thebutton input unit is coupled to the processing unit 5206, and theprocessing unit 5206 is further configured to receive input from thebutton input unit, and wherein the event includes a press on the buttoninput unit on the device 5200. In some embodiments, the event includes atouch on the touch-sensitive surface (e.g., touch-sensitive surface unit5204).

The operations described above with reference to FIG. 27F are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.52. For example, setting operation 2752, receiving operation 2754, andsetting operation 2756 may be implemented by event sorter 170, eventrecognizer 180, and event handler 190. Event monitor 171 in event sorter170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

Attention is now directed toward embodiments of user interfaces andassociated processes that may be implemented on an electronic device,such as device 100, 300, or 500.

FIGS. 53A-53F illustrate exemplary user interfaces. FIGS. 54A-54E areflow diagrams illustrating exemplary methods. The user interfaces inFIGS. 53C-53F are used to illustrate the processes in FIGS. 54A-54E.

FIGS. 53A-53F depict device 5300, which in some embodiments includessome or all of the features described with respect to devices 100, 300,and/or 500. In some embodiments, device 5300 has touch-sensitive andpressure-sensitive display 5302 (sometimes simply called atouch-screen). In some embodiments, device 5300 has rotatable anddepressible input mechanism 5304. In some embodiments, device 5300 hasdepressible input mechanism 5306. Display 5302 and input mechanisms 5304and 5306 may share some or all characteristics, respectively, withdisplay 504 and input mechanisms 506 and 508.

In some embodiments, device 5300 includes an attachment mechanism forattaching, affixing, or connecting a device to a body part or toclothing of a user. In this manner, device 5300 may be considered a“wearable device,” sometimes simply referred to as a “wearable.” In theexamples of FIGS. 53A and 53B, device 5300 may comprise a wrist strap(not pictured), which may be used to affix the device to the wrist of auser. In some embodiments, device 5300 takes the form factor of a “smartwatch,” a portable electronic device configured to be affixed by a strapto the wrist of a user.

Attention is now directed toward techniques for accessing and presentinginformation corresponding to past times and future times. In someembodiments, a user interface is configured to present information inthe form of complications, which may be visually displayed userinterface objects sharing any or all of the characteristics ofcomplications discussed above in this disclosure.

In some embodiments, a user may access a “time scrubbing” mode or a“time travel” mode, and associated user interfaces. In “time scrubbing”or “time travel” mode, a user may advance or rewind a non-current time,also called a “scrubbing time.” “Scrubbing” may refer to the action ofprogressing through time forward, or progressing through time backward.A user may “scrub forward” as he causes a scrubbing time to advancefurther into the future (as if fast-forwarding), and a user may “scrubbackward” as he causes a scrubbing time to move further into the past(as if rewinding). Rather than corresponding to the current time of day(or to a time somewhere else in the world), the scrubbing time may beset in accordance with a user input. As the user sets and updates thescrubbing time (e.g., as the user scrubs), the information displayed ininterfaces associated with time-scrubbing mode may be updated inaccordance with the scrubbing time. Namely, the scrubbing time may bedisplayed on the time scrubbing interface, and a difference between thescrubbing time and the current time may be displayed on the timescrubbing interface. In some embodiments, an indicator of the differencebetween the current time and the scrubbing time is displayed. In someembodiments, one or more complications may be updated in accordance withthe scrubbing time, such that the complications, while the device is intime-scrubbing mode, display information corresponding to the scrubbingtime rather than information corresponding to the current time. In thisway, the device may appear to “travel” through time as the scrubbingtime advances into the future or rewinds into the past, and thedisplayed complications are updated accordingly. In some embodiments,the complications may display forecasted or predicted informationcorresponding to a scrubbing time in the future, and may displayrecorded or historical information corresponding to a scrubbing time inthe past.

Features described can allow a user to use time-scrubbing mode toquickly, easily, and intuitively access past and future informationcorresponding to a plurality of displayed complications; the user mayeasily view information corresponding to more than one complication forthe same point in the future or point in the past, and may appreciatethe manner in which the information corresponding to differentcomplications did or will interrelate by virtue of corresponding to thesame scrubbing time. For example, a user may scrub forward in time tosee that a calendar event later in the day corresponds to a forecastedthunderstorm; information which the user may not have appreciated if theuser viewed the future event in a calendar application interface and theforecasted weather in a separate weather application interface.

Attention is now specifically directed to interfaces for time scrubbinga likeness of an analog clock face.

FIG. 53A depicts exemplary user interface 5340, displayed on display5302 of device 5300. In some embodiments, user interface 5340 is a watchface interface screen, such as a home interface of a wearablesmart-watch portable electronic device. Interface 5340 includes watchface 5308, which is a displayed likeness of an analog watch face. Watchface 5308 includes hour hand 5310 a and minute hand 5310 b. In someembodiments, watch face 5308 may further include a second hand. In FIG.53A, hour hand 5310 a and minute hand 5310 b indicate that the currenttime is 11:09.

Interface 5340 further includes weather complication 5312, which is acomplication configured to indicate weather data for a user-selectedlocation. In some embodiments, weather complication 5312 may beassociated with a weather application from which it draws weather data.In some embodiments, weather complication 5312 may be a selectableaffordance, such that detection of a user input at a location on display5302 corresponding to weather complication 5312 may cause an associatedinterface to be displayed, additional information to be displayed, or anassociated application (e.g., a weather application) to be accessed oropened. In some embodiments, weather complication 5312 may displayinformation about the temperature, the precipitation, the wind speed,the cloud cover, or any other relevant or useful weather information.

In some embodiments, weather complication 5312 may display informationcorresponding to present information, to future information (e.g.,future scheduled events, predicted/forecasted information, etc.), or topast information (e.g., historical information, recorded events, pastevents, past predictions/forecasts, etc.). In the depicted example,weather complication 5312 is displaying current weather information,indicating that the current air temperature is 72°.

Interface 5340 further includes stock-market complication 5314, which isa complication configured to indicate stock-market data. In someembodiments, stock-market complication 5314 may be associated with astock-market application from which it draws stock-market data. In someembodiments, stock-market complication 5314 may be a selectableaffordance, such that detection of a user input at a location on display5302 corresponding to stock-market complication 5314 may cause anassociated interface to be displayed, additional information to bedisplayed, or an associated application (e.g., a stock-marketapplication) to be accessed or opened. In some embodiments, stock-marketcomplication 5314 may display information about one or more stocks, oneor more markets or indexes, one or more portfolios, or any otherrelevant or useful stock-market information.

In some embodiments, stock-market complication 5314 may displayinformation corresponding to present information or to past information(e.g., historical information, recorded events, past events, or pastpredictions/forecasts). In some embodiments, stock-market complication5314 may be incapable of displaying information corresponding to futureinformation, as future stock-market information may be un-knowable. Insome embodiments, stock-market complication 5314 may be configured todisplay certain future information, such as scheduled future purchasesor sales, scheduled future events (e.g., markets opening), or projectedor predicted future stock market performances. In the depicted example,stock-market complication 5314 is displaying current stock-marketinformation, indicating that the NASDAQ is up 2.45 points on the day.

FIG. 53A further depicts user input 5316 a, which is a touch contactdetected by touch-sensitive display 5302. Touch contact input 5316 a maybe a single-touch input, a multi-touch input, a single-tap input, and/ora multi-tap input detected by touch- and/or pressure-sensitive elementsin display 5302. In the displayed example, input 5316 a is asingle-finger, single-tap input detected at a location on display 5302corresponding to displayed watch face 5308. Device 5300 may beconfigured, in some embodiments, to, in response to detecting user input5316 a (or any other suitable predefined user input, including rotationof a rotatable input mechanism) activate a time-scrubbing mode.

FIG. 53B depicts exemplary user interface 5350, displayed on display5302 of device 5300. Exemplary user interface 5350 shows the manner inwhich, in some embodiments, device 5300 responds to the detection ofinput 5316 a in FIG. 53A. Namely, user interface 5350 shows theactivation, by device 5300, of a time-scrubbing mode and an associatedtime scrubbing interface in accordance with some embodiments.

In the depicted example, interface 5350 retains many of the sameelements and features of interface 5340, including the same prominentwatch face 5308, and the same complications 5312 and 5314. In someembodiments, the visual appearance of one or more of the elements ofinterface 5350 differs from the appearance of a corresponding orassociated element in interface 5340, so as to indicate thattime-scrubbing mode has been activated.

In some embodiments, time-scrubbing mode is a mode of operation of adevice in which a user may indicate, by one or more user inputs, a timeother than a current time. In accordance with the user's indication of apast or future time, a device may display an indication of the user'sindicated time, and may update one or more user interface objects inaccordance with the user's indicated time. The updated user interfaceobjects, such as complications, affordances, icons, or the like, may beupdated to show information that corresponds to the user's indicatedtime, which may be called a scrubbing time. Thus, in some embodiments,as a user “scrubs” forward or backward in time, the scrubbing time iscontinuously updated, and other information displayed on an interface iscorrespondingly continuously updated, such that the informationdisplayed on the display continuously corresponds to the scrubbing time.In the depicted example of activating and using a time-scrubbing mode ofFIGS. 53A-53C, described in greater detail below, a user uses arotational user input to scrub forward in time from 11:09 (the currenttime) to 11:34 (a future scrubbing time). In accordance with the forwardscrubbing, complications 5312 and 5314 are updated to correspond to thefuture scrubbing time, with weather complication 5312 displaying aforecasted air temperature and stock-market complication 5314 ceasing tobe displayed (to indicate that future information is unavailable).

In the depicted example, interface 5350 differs from interface 5340 inthat, in the place of clock hands 5310 a and 5310 b, interface 5350includes scrubbing hour hand 5322 a and scrubbing minute hand 5322 b. Insome embodiments, scrubbing hands may be displayed in place of or inaddition to non-scrubbing hands (e.g., hands indicating the currenttime). In some embodiments, scrubbing hands may have the same visualappearance as current-time hands, or may have a different appearancefrom current-time hands. For example, scrubbing hands may be displayedin a different size, shape, color, highlighting, or animation style ascurrent-time hands. In some embodiments, for example, current-time hands(e.g., hands 5310 a and 5310 b in FIG. 53A) may be displayed in white,while scrubbing hands (e.g., hands 5322 a and 5322 b) may be displayedin green.

In the depicted example, interface 5350 further differs from interface5340 by including digital clock face 5317, which displays the currenttime (11:09). Interface 5350 further differs from interface 5340 byincluding time difference indicator 5318, which displays an indicationof the difference between the current time and the scrubbing time. Inthe example shown, the scrubbing time is 11:09 and the current time isalso 11:09, as the scrubbing time has not yet been moved away from thecurrent time. Therefore, time difference indicator 5318 indicates thatthere is no difference between the current time and the scrubbing timeby indicating a difference of “+0” minutes.

FIG. 53B further depicts rotational input 5320 a, which is a rotationaluser input detected by rotational input mechanism 5304 of device 5300.Rotational user input 5320 a may include one or more rotations ofrotational input mechanism 5304, the one or more rotations each havingone or more speeds, accelerations, directions, durations, and spacingsrelative to one another. The one or more rotations may together form apredefined rotation pattern constituting an input. In the depictedexample, rotational input 5320 a is a single rotation of rotatable inputmechanism 5304 in a clockwise direction as defined if looking at theface of the rotatable input mechanism from in the plane of the page tothe left of the figure. (That is, the illustrated direction of rotationis such that rotatable input mechanism 5304 is being rotated into theplane of the page in the z-axis direction at the top of rotatable inputmechanism 5304, while it is being rotated out of the plane of the pagein the z-axis direction at the bottom of rotatable input mechanism5304.) In some embodiments, rotational input 5320 a is an input forscrubbing forward to a future time.

FIG. 53C depicts exemplary user interface 5360 displayed on display 5302of device 5300. Exemplary user interface 5360 shows the manner in which,in some embodiments, device 5300 responds to the detection of input 5320a in FIG. 53B. Namely, user interface 5360 shows time scrubbing to afuture time, by device 5300, and an associated interface in accordancewith some embodiments. Specifically, interface 5360 depicts how watchface 5308 (and hands 5310 a, 5310 b, 5322 a, and 5322 b) andcomplications 5312 and 5314 are updated in accordance with timescrubbing.

First, in the depicted example, in accordance with user input 5320 a,scrubbing hands 5322 a and 5322 b are moved forward to indicate thescrubbing time. In some embodiments, scrubbing hands may be movedcontinuously, smoothly, or regularly to match a rotational user input,such that the further and faster a rotational input rotates, the furtherand faster scrubbing hands may advance. In some embodiments, scrubbinghands may sweep from a previous position into a current position,simulating the appearance of watch hands sweeping into a new position asthe watch is set to a new time by rotating a watch crown. In thedepicted example, scrubbing hour hand 5322 a and scrubbing minute hand5322 b have swept from their previous position in interface 5350 totheir new position in interface 5360 (as indicated by the arced arrowshowing the movement of scrubbing hour hand 5322 b) in accordance withthe detection of rotational user input 5320 a in FIG. 53B.

Further, in the depicted example, as scrubbing hands 5322 a and 5322 bsweep forward as the scrubbing time is advanced into the future, hands5310 a and 5310 b, which are current-time hands, are revealed in theirplace. In some embodiments, hands 5310 a and 5310 b are identical inappearance as they were in interface 5340 in FIG. 53A. In someembodiments, hands 5310 a and 5310 b are displayed in a manner tovisually indicate that time-scrubbing mode is active, such as byvisually distinguishing the hands 5310 a and 5310 b from theirappearance when time-scrubbing mode was not active, such as by beingdisplayed in a different size, shape, color, highlighting, or animationstyle. In the depicted embodiment, hands 5310 a and 5310 b are displayedin a white color before the activation of time-scrubbing mode, whilethey are displayed in a gray, partially translucent color intime-scrubbing mode; this gray translucent color is indicated by thehash pattern on hands 5310 a and 5310 b in FIG. 53C. In the depictedexample, hands 5310 a and 5310 b are displayed as being “behind”scrubbing hands 5322 a and 5322 b, as shown by hour scrubbing hand 5322a occluding hour hand 5310 a where the two hands partially overlap; thisarrangement may help emphasize scrubbing hands while in time-scrubbingmode, as the scrubbing hands may be central to the functionality of timescrubbing and may correspond to other information displayed on ascrubbing interface.

Further, in the depicted example, digital clock face 5317 and timedifference indicator 5318 have been updated in accordance with thescrubbing time. In the depicted example of interface 5360, digital clockface 5317 has been updated to indicate the new scrubbing time of 11:34,and time difference indicator has been updated to indicate thedifference between the current time (11:09) and the scrubbing time(11:34) of “+25” minutes. In some embodiments, user interface objectssuch as digital clock face 5317 and time difference indicator 5318 maybe continuously or intermittently updated as a user scrubs forward orbackward in time. Updates may be displayed for each changing second, 15seconds, minute, 5 minutes, hour, or the like. In some embodiments, oneor more animations may be used to depict text or numerals changing asthe user scrubs forward or backward in time. In some embodiments, text,numerals, or other characters or elements of a user interface object maybe suddenly replaced by a new character as scrubbing is performed, suchthat the “09” in 11:09 would cease to be displayed and be immediatelyreplaced by a “10.” In some embodiments, one or more characters or otherelements of a user interface object may transition by way of ananimation; for example, old elements or characters may fade away bybecoming increasingly translucent, may shrink in size, may translate inone or more directions, and/or may be displayed as “flipping” out ofview to simulate the appearance of a flap-display, split-flap display,or arrival/departure board; new elements or characters may, for example,fade into view by becoming decreasingly translucent, may grow in size,may translate in one or more directions, and/or may be displayed as“flipping” into view to simulate the appearance of a flap-display,split-flap display, or arrival/departure board. In some embodiments, anyof the animations described above or elsewhere in this disclosure may bereversed, such that an animation may be displayed in a first order whena user is scrubbing in a first direction, and the animation may bedisplayed in the opposite order (as if rewinding a video) when a user isscrubbing in the opposite direction.

Further, in the depicted example of FIG. 53C, complications 5312 and5314 have been updated in accordance with the scrubbing to a futuretime, such that the displayed (or newly undisplayed) complicationscorrespond to the displayed scrubbing time by displaying informationrelated to the displayed scrubbing time. Complications may be updated intime-scrubbing mode such that the information displayed by thecomplication corresponds to the currently displayed scrubbing time,rather than the current time. An update to a complication may include,as compared to when the device was not in time-scrubbing mode or wasscrubbed to a different scrubbing time, displaying differentinformation, ceasing to display information, or beginning to displayinformation after having ceased to display information.

For example, when a scrubbing time is a future time, displayedcomplications may display future scheduled events such as futurecalendar events, may display forecasted or projected information (suchas a weather forecast) or may indicate a lack of availability ofinformation corresponding to the future time. In the case of a lack ofavailability of information corresponding to a future time, acomplication may affirmatively indicate that no information is availablevia displayed text or symbol, the complication may cease to be displayedto indicate that no information is available, or the complication may be“freeze” and/or be displayed in a manner so as to indicate that theinformation displayed in the frozen state does not correspond to thefuture time (e.g., a complication may be grayed out or faded out withthe future-most available information displayed, if the complication isscrubbed so far into the future that no information for the scrubbingtime is available).

When a scrubbing time is a past time, displayed complications maydisplay past scheduled events such as a past calendar event, may displaypreviously projected information such as a past weather forecast (e.g.,in the absence of available historical data), or may indicate a lack ofavailability of information corresponding to the past time. In the caseof a lack of availability of information corresponding to a past time, acomplication may affirmatively indicate that no information is availablevia displayed text or symbol, the complication may cease to be displayedto indicate that no information is available, or the complication may be“freeze” and/or be displayed in a manner so as to indicate that theinformation displayed in the frozen state does not correspond to thepast time (e.g., a complication may be grayed out or faded out with theoldest available information displayed, if the complication is scrubbedso far into the past that no information for the scrubbing time isavailable).

In some embodiments, a complication may cease to display informationwhen no information is available for or relevant to a certain period oftime. For example, if a complication relates to a daily performance of astock index, then, as a user scrubs backwards through time, thecomplication may cease to display any information when the user scrubsto the early morning hours, or to a weekend, when the stock market wasnot open and no daily performance is considered relevant. As a usercontinues to scrub in the same direction, relevant information may againbe displayed as the user scrubs through additional scrubbing times, suchas reaching another period when the stock market was open and beginningto display a daily performance for the stock index for that day andtime.

In the example depicted in FIG. 53C, a user is scrubbing forward in time(the current time being 11:09, as indicated by hands 5310 a and 5310 b)and has reached 11:34 (as indicated by digital clock face 5317 andscrubbing hands 5322 a and 5322 b) with a time offset of plus 25 minutes(as indicated by time difference indicator 5318). As the user hasscrubbed forward in time by 25 minutes, weather complication 5312 hasbeen updated to reflect a weather forecast for 25 minutes in the future,when it is predicted to be one degree warmer, at 73° rather than thecurrent 72° (as indicated in interface 5350 in FIG. 53B). As the userhas scrubbed forward in time by 25 minutes, stock-market complication5314 has been updated to reflect the fact that information about thefuture performance of the NASDAQ is unavailable; the lack of informationis conveyed by the stock-market complication 5314, as shown in interface5350 in FIG. 53B, ceasing to be displayed in interface 5360 in FIG. 53C.

FIG. 53C further depicts user input 5336 a, which is a touch contactdetected by touch-sensitive display 5302. Touch contact input 5336 a maybe a single-touch input, a multi-touch input, a single-tap input, and/ora multi-tap input detected by touch- and/or pressure-sensitive elementsin display 5302. In the displayed example, input 5336 a is asingle-finger, single-tap input detected at a location on display 5302corresponding to displayed weather complication. In some embodiments, inresponse to detecting user input 5336 a, device 5300 may provideadditional information, additional interfaces, or additional modescorresponding to weather complication 5312. For example, device 5300 maylaunch a weather application associated with weather complication 5312.In some embodiments, device 5300 may provide additional information,additional interfaces, or additional modes corresponding to a selectedcomplication and to the scrubbing time. For example, in response to auser tapping a weather complication when the device is scrubbed to apast time, an interface of a weather application showing historicalweather data for the scrubbed-to past time may be displayed; in responseto a user tapping a weather complication when the device is scrubbed toa future time, an interface of a weather application showing forecastedweather for the scrubbed-to future time may be displayed. In thedepicted example, in response to detecting user input 5336 a, device5300 may provide current weather information (because the scrubbing timeis so close to the present, e.g., below a predefined threshold amount oftime into the future) in some embodiments, or it may provide forecastedweather information associated with the scrubbing time of 11:34 in someembodiments.

FIG. 53C further depicts user inputs 5324 a and 5324 b, both of whichare user inputs configured to cause device 5300 to exit time-scrubbingmode and return to a non-time-scrubbing interface. In some embodiments,any suitable user input may be predetermined to cause a device to exittime-scrubbing mode. In the depicted example, user input 5324 a is atouch contact detected on display 5302. In some embodiments, user input5324 a may be a single-touch input, a multi-touch input, a single-tapinput, and/or a multi-tap input detected by touch- and/orpressure-sensitive elements in display 5302. In some embodiments, userinput 5324 a is a single-tap input detected at a location correspondingto digital clock face 5317 and/or time difference indicator 5318. In thedepicted example, user input 5324 b is a depression input detected byrotatable and depressible input mechanism 5304. In some embodiments,user input 5324 b may be a single-press input or a multi-press inputdetected by a rotatable and depressible input mechanism. In someembodiments, user input 5324 b is a single-press input detected bydepressible and rotatable input mechanism 5304.

In response to detecting either user input 5324 a or 5324 b, or anyother suitable predetermined user input, device 5300 may causetime-scrubbing mode to be ceased and may cease to display time scrubbinginterfaces. In some embodiments, updated complications may return totheir original appearance before time-scrubbing mode was engaged, or maychange to an appearance corresponding to a new current time other thanthe current time that was current when time-scrubbing mode was engaged.In some embodiments, indications that time-scrubbing mode is active,such as digital clock face 5317, time difference indicator 5318, andscrubbing hands 5322 a and 5322 b may cease to be displayed. In someembodiments, hands corresponding to a current time, such as hands 5310 aand 5310 b, may return to their original visual appearance and stylefrom before time-scrubbing mode was engaged. Any of these changes may bemade by way of any of the animations described above, including areversed and/or accelerated version of any such animation. In thedepicted example, in response to detecting user input 5324 a or 5324 b,device 5300 ceases to display user interface 5360 and displays userinterface 5340 again; user interface 5340 indicates that the currenttime is still 11:09 and that the information corresponding to bothweather complication 5312 (72°) and stock-market complication 5314(NASDAQ +2.45) has not changed since time-scrubbing mode was activated.

Attention is now specifically directed to interfaces for time scrubbinga digital clock face. In the depicted example of activating and using atime-scrubbing mode of FIGS. 53D-53F, described in greater detail below,a user uses a rotational user input to scrub forward in time from 11:09(the current time) to 11:34 (a future scrubbing time). In accordancewith the forward scrubbing, complications 5312 and 5314 are updated tocorrespond to the future scrubbing time, with weather complication 5312displaying a forecasted air temperature and stock-market complication5314 ceasing to be displayed (to indicate that future information isunavailable).

FIG. 53D depicts exemplary user interface 5370, displayed on display5302 of device 5300. In some embodiments, user interface 5370 is a watchface interface screen, such as a home interface of a wearablesmart-watch portable electronic device. In some embodiments, interface5370 may be displayed by device 5300 in response to a user (such as auser of a device displaying interface 5340 as described in FIG. 53A)selecting a different “face” for device 5300, for example causinginterface 5340 to cease to be displayed and interface 5370 to begin tobe displayed. Interface 5370 may share some common elements withinterface 5340, namely weather complication 5312 and stock-marketcomplication 5314. In some embodiments, complications 5312 and 5314 ininterface 5370 may have some or all of the attributes as described abovewith reference to interface 5340 in FIG. 53A.

Interface 5370 includes digital watch face 5328, which is indicatingthat the current time is 11:09. Interface 5370 also includes day/dateobject 5326, which is indicating that the current day of the week isTuesday and that the current date is July 10. In some embodiments,day/date object 5326 may be considered a complication, and may bereferred to as a day/date complication.

FIG. 53D further depicts user input 5316 b, which is a touch contactdetected by touch-sensitive display 5302. Touch contact input 5316 b maybe a single-touch input, a multi-touch input, a single-tap input, and/ora multi-tap input detected by touch- and/or pressure-sensitive elementsin display 5302. In the displayed example, input 5316 b is asingle-finger, single-tap input detected at a location on display 5302corresponding to digital clock face 5328. Device 5300 may be configured,in some embodiments, to, in response to detecting user input 5316 b (orany other suitable predefined user input, including rotation of arotatable input mechanism), activate a time-scrubbing mode.

FIG. 53E depicts exemplary user interface 5380, displayed on display5302 of device 5300. Exemplary user interface 5380 shows the manner inwhich, in some embodiments, device 5300 responds to the detection ofinput 5316 b in FIG. 53D. Namely, user interface 5380 shows theactivation, by device 5300, of a time-scrubbing mode and an associatedtime scrubbing interface in accordance with some embodiments.

In the depicted example, interface 5380 includes object 5326 andcomplications 5312 and 5314 in the same manner as described above withreference to interface 5370 in FIG. 53D. In some embodiments, object5326 and complications 5312 and 5314 may be visually distinguished inone or more ways from their respective appearances in interface 5370 inFIG. 53D to indicate that time-scrubbing mode is active.

In the depicted example, interface 5380 differs from interface 5370 inseveral ways that indicate that time-scrubbing mode has been activated.In the depicted example, interface 5380 differs from interface 5370 inthat digital clock face 5328 has translated to the top right corner ofdisplay 5302 (as indicated by the diagonal arrow) and has decreased insize. In some embodiments, this transition may include an animation ofthe translation and the resizing. In some embodiments, when digitalclock face 5328 is moved from its position in interface 5370 to itsposition in interface 5380, it may be displayed in a different size,shape, color, highlighting, or animation style. In some embodiments, theshape, color, highlighting, and/or animation style of digital clock face5328 may remain unchanged as digital clock face translates and isresized between interface 5370 in FIG. 53D and interface 5380 in FIG.53E. In some embodiments, digital clock face 5328 may appear in a whitecolor in both interfaces 5370 and interface 5380.

In some embodiments, when digital clock face 5328 transitions to the topcorner of display 5302 as time-scrubbing mode is activated, a visualindicator indicating that digital clock face 5328 indicates a currenttime may be displayed. In the depicted example, the word “NOW” isdisplayed on display 5302 near the top left corner of display 5302. Insome embodiments, the visual indicator, such as the word “NOW,” may bedisplayed in a similar or identical visual style as digital clock face5328 following its transition into its position in interface 5380. Forexample, the word “NOW” may be displayed in a similar size, font, color,highlighting, and/or animation style as digital clock face 5328 ininterface 5380. In the depicted example, the word “NOW” or anotherindicator may appear in a white color when digital clock face 5328appears in a white color.

In the depicted example, interface 5380 further differs from interface5370 by including digital clock face 5332, which is a second digitalclock face that has appeared in the position on display 5302 that waspreviously occupied by digital clock face 5328 (before its transitionand resizing) in interface 5370 in FIG. 53D. In some embodiments,digital clock face 5332 displays the scrubbing time of time-scrubbingmode, which currently is 11:09, the same as the current time, as theuser has not entered any input causing the scrubbing time to advanceinto the future or rewind into the past. In some embodiments, digitalclock face 5332 may be displayed in the same or similar visual style asdigital clock face 5328, including by being displayed in the same size,font, color, highlighting, and/or animation style. In some embodiments,digital clock face 5332 may be displayed in a different visual stylethan digital clock face 5328 in interface 5370, to indicate to the userthat digital clock face 5332 indicates a scrubbing time rather than acurrent time, such as by being displayed in a green color rather than awhite color. In some embodiments, digital clock face 5332 may appear oninterface 5380 in response to the activation of time-scrubbing mode inaccordance with any of the animations discussed above with reference tocomplications being updated during scrubbing. In some embodiments, theanimation of digital clock face 5332 appearing in interface 5380 mayinclude digital clock face 5380 increasing in size and/or graduallybecoming less translucent (e.g., fading in).

FIG. 53E further depicts rotational input 5320 b, which is a rotationaluser input detected by rotational input mechanism 5304 of device 5300.In some embodiments, rotational user input 5320 b may have one or morecharacteristics in common with rotational input 5320 a described abovewith reference to FIG. 53B. In some embodiments, rotational input 5320 bis an input for scrubbing forward to a future time.

FIG. 53F depicts exemplary user interface 5390 displayed on display 5302of device 5300. Exemplary user interface 5390 shows the manner in which,in some embodiments, device 5300 responds to the detection of input 5320b in FIG. 53E. Namely, user interface 5390 shows time scrubbing to afuture time by device 5300 and an associated interface in accordancewith some embodiments. Specifically, interface 5390 depicts how digitalclock face 5332 and complications 5312 and 5314 are updated inaccordance with time scrubbing.

First, in the depicted example, in accordance with user input 5320 b,digital clock face 5332 has changed from displaying “11:09” to insteaddisplaying “11:24,” thereby indicating the scrubbing time. In someembodiments, a digital clock face may be stepped forward in accordancewith a rotational user input, such that the further and faster arotational input rotates, the further and faster a digital clock faceindicating a scrubbing time may advance. In some embodiments, displayednumerals on a digital clock face may change iteratively, such as oncefor every minute scrubbed, once for every five minutes scrubbed, or thelike. Updates may be displayed for each changing second, 15 seconds,minute, 5 minutes, hour, or the like. In some embodiments, displayednumerals on a digital clock face may change gradually or smoothly, suchas by fading into and out of view or translating into or out of view. Insome embodiments, displayed numerals on a digital clock face may beanimated as changing individually (e.g., number by number), and in someembodiments displayed numerals on a digital clock face may be animatedas changing as a group (e.g., part of, or the entire, digital clock facechanges together). In some embodiments, one or more of the numerals orother elements displayed as part of a digital clock face, includingdigital clock face 5332, may change in any of the manners describedabove with reference to digital clock face 5317 and FIG. 53C, includingby way of an animation simulating the appearance of a flap-display,split-flap display, or arrival/departure board.

Further, in the depicted example, as digital clock face 5332 advancesfurther as the scrubbing time is advanced into the future, digital clockface 5328 may remain fixed and continue to display the current time. (Ifthe current time advances with the passage of time, digital clock face5328 may accordingly advance, and a scrubbing clock face such as digitalclock face 5332 may also accordingly advance to maintain the same offsetbetween the current time and the scrubbing time.) In some embodiments, atime difference indicator may be displayed as part of user interface5390 (and/or 5380 in FIG. 53E), and the time difference indicator may beupdated (in accordance, in some embodiments, with any of the animationsor display styles discussed above, including those discussed withreference to digital clock face 5332 and/or those discussed withreference to digital clock face 5317 and FIG. 53C) to display an updatedtime difference in accordance with the scrubbing time advancing furtherinto the future. If user interface 5390 included a time differenceindicator, for example, it would be updated in accordance with the timebeing scrubbed forward to indicate a positive 25 minute differencebetween the scrubbing time of 11:34 and the current time of 11:09.

Further, in the depicted example of FIG. 53F, complications 5312 and5314 have been updated in the same manner as described above withreference to interface 5360 in FIG. 53C, so as to correspond to thescrubbing time of 11:34 rather than the current time of 11:09. In someembodiments, day/date object 5326 may also be updated in accordance witha scrubbing time in time-scrubbing mode; for example, if a user scrubsfar enough into the future or the past to reach a different day, thenday/date object 5326 may be updated in a same or similar manner as acomplication may be updated to reflect the change to the day and date.

FIG. 53F further depicts user input 5336 b, which is a touch contactdetected by touch-sensitive display 5302. Touch contact input 5336 b maybe a single-touch input, a multi-touch input, a single-tap input, and/ora multi-tap input detected by touch- and/or pressure-sensitive elementsin display 5302. In the displayed example, input 5336 b is asingle-finger, single-tap input detected at a location on display 5302corresponding to displayed weather complication. In some embodiments, inresponse to detecting user input 5336 a, device 5300 may provideadditional information, additional interfaces, or additional modescorresponding to weather complication 5312, including in any of themanners described above with respect to input 5336 a and FIG. 53C.

FIG. 53F further depicts user inputs 5334 a and 5334 b, both of whichare user inputs configured to cause device 5300 to exit time-scrubbingmode and return to a non-time-scrubbing interface. In some embodiments,any suitable user input may be predetermined to cause a device to exittime-scrubbing mode. In some embodiments, user inputs 5334 a and 5334 bmay share some or all characteristics with user inputs 5324 a and 5324 bdescribed above, respectively.

In response to detecting either user input 5334 a or 5334 b, or anyother suitable predetermined user input, device 5300 may causetime-scrubbing mode to be ceased and may cease to display time scrubbinginterfaces. In some embodiments, updated complications may return totheir original appearance before time-scrubbing mode was engaged, or maychange to an appearance corresponding to a new current time other thanthe current time that was current when time-scrubbing mode was engaged.In some embodiments, indications that time-scrubbing mode is active,such as digital clock face 5332, may cease to be displayed, and userinterface objects that moved position and/or changed appearance, such asdigital clock face 5328, may return to their original visual appearanceand style from before time-scrubbing mode was activated. Any of thesechanges may be made by way of any of the animations described above,including a reversed and/or accelerated version of any such animation.In the depicted example, in response to detecting user input 5334 a or5334 b, device 5300 ceases to display user interface 5390 and displaysuser interface 5370 again; user interface 5370 indicates that thecurrent time is still 11:09 and that the information corresponding toboth weather complication 5312 (72°) and stock-market complication 5314(NASDAQ +2.45) has not changed since time-scrubbing mode was activated.

FIGS. 54A-54E are flow diagrams illustrating a method for accessing andpresenting information corresponding to past times and future times.Method 700 is performed at a device (e.g., 100, 300, 500, 5300) with adisplay and a rotatable input mechanism. Some operations in method 700may be combined, the order of some operations may be changed, and someoperations may be omitted.

As described below, method 700 provides an intuitive way to access andpresent information corresponding to past times and future times. Themethod reduces the cognitive burden on a user for accessing andpresenting information corresponding to past times and future times,thereby creating a more efficient human-machine interface. Forbattery-operated computing devices, enabling a user to access andpresent information corresponding to past times and future times, suchas in a time-scrubbing mode in which displayed complications may bescrubbed forward and/or backward in time, conserves power and increasesthe time between battery charges, by reducing the number of inputsrequired, reducing processing power used, and/or reducing the time ofusage of the device.

In some embodiments, a device may display a current-time indicatordisplaying a current time. In response to a user input (such as a tap ona touch-sensitive display on the current-time indicator), the device maydisplay, in addition to the current-time indicator, a non-current-timeindicator. In response to and in accordance with a user input (such as arotation of a rotatable input mechanism such as a crown of a smartwatch), the time displayed by the non-current-time indicator may bescrubbed forward or backward. In accordance with the scrubbing of thenon-current time to a future or past time, one or more complications orother user interface objects may be updated to correspond to thenon-current time, by displaying information relating to the complicationand correlating to the non-current time rather than the current time.

In FIG. 54A, at block 5402, method 700 is performed at an electronicdevice having a display and a rotatable input mechanism. An exemplarydevice is device 5300 of FIGS. 53A-53F, which has display 5302 and has arotatable input mechanism 5304.

A block 5404, the device displays a first current-time indicatorindicating a current time. In some embodiments, a current-time indicatoris any watch face, clock face, or other indication of a time that isconfigured, designed, or understood to display a current time, such asthe current time of day in the timezone in which a user is currentlylocated. In some situations, a current-time indicator may be displayinga non-current time, such as when the watch is not set for the correcttime; however, in most situations, a current-time indicator will displaythe correct current time. In the example of interface 5340 in FIG. 53A,watch face 5308 and clock hands 5310 a and 5310 b together form acurrent-time indicator, indicating that the current time is 11:09. Inthe example of interface 5370 in FIG. 53D, digital clock face 5328 is acurrent-time indicator, indicating that the current time is 11:09.

At block 5406, the device displays a first user interface objectconfigured to display information corresponding to the current time,wherein the information corresponding to the current time pertains to afirst information source and is information other than a day, time, ordate of the current time. In some embodiments, the first user interfaceobject may be a complication, as described above, and may be configuredto display information corresponding to a certain subject matter or acertain information source. In some embodiments, complications maycorrespond to weather information, to stock market information, tocalendar information, to day/date information, to time information, toworld clock information, to social media information, to messageinformation, to email information, to pedometer information, tohealth/fitness information, to exercise information, to alarminformation, to stopwatch information, to information associated withthird-party applications, or to any other suitable information that maybe visually presented as part of a complication or other user interfaceobject. In the examples of interfaces 5340 and 5370 in FIGS. 53A and53D, weather complication 5312 is a user interface object configured todisplay information corresponding to the current time (e.g., currentinformation), the information pertaining to a weather application and/ora source of weather data in some embodiments. In some embodiments,weather complication 5312 may be configured to display current weatherinformation for the current time, such as a current air temperature(e.g., 72°). In the examples of interfaces 5340 and 5370 in FIGS. 53Aand 53D, stock-market complication 5314 is a user interface objectconfigured to display information corresponding to the current time(e.g., current information), the information pertaining to astock-market application and/or a source of stock-market data, in someembodiments. In some embodiments, stock-market complication 5314 may beconfigured to display a current performance of the NASDAQ, such aspoints gained or lost on the current day of trading (e.g., plus 2.45points).

In some embodiments, user interface objects or complications may beconfigured to display information that is the most current informationavailable, such as a most recent temperature reading or a most recentstock score. In some embodiments, user interface objects orcomplications may be configured to display information that explicitlyrelates to the current time, such as a calendar event that is occurringat the current time, or a proximate calendar event that is occurring ata time in the near future or a time in the near past with reference tothe current time.

At block 5408, optionally, the device detects a first touch contact at alocation corresponding to the first current-time indicator. In someembodiments, the input may be one or more touch contacts detected by atouch-sensitive and/or pressure-sensitive surface, such as atouch-screen. In some embodiments, the first touch contact may bedetected at a location on a touch-screen at which the first current-timeindicator is currently displayed. In some embodiments, a user may tap acurrent-time indicator such as a displayed watch face or a digital clockface, and a device may responsively activate a time-scrubbing mode anddisplay associated time-scrubbing interfaces. In the example ofinterface 5340 in FIG. 53A, device 5300 detects user input 5316 a, whichis a touch contact detected by touch-sensitive display 5302. In someembodiments, user input 5316 a is a single-finger single-tap gesturedetected at a location of display 5302 at which watch face 5308 iscurrently displayed. In the example of interface 5370 in FIG. 53D,device 5300 detects user input 5316 b, which is a touch contact detectedby touch-sensitive display 5302. In some embodiments, user input 5316 bis a single-finger single-tap gesture detected at a location of display5302 at which digital clock face 5328 is currently displayed.

At block 5410, optionally, in response to detecting the first touchcontact, the device displays a non-current-time indicator indicating thecurrent time. In some embodiments, when time-scrubbing mode isactivated, a non-current-time indicator is displayed. A non-current-timeindicator may be any watch face, clock face, or other indication of atime that is configured, designed, or understood to display anon-current time. In some embodiments, a non-current-time indicator mayindicate a “scrubbing time” that is displayed when time-scrubbing modeis activated; the scrubbing time may be a time that is set in accordancewith user inputs and is used to change what information is displayed bycomplications or other user interface objects during time-scrubbingmode. In some embodiments, the non-current-time indicator may suddenlyappear upon the activation of time-scrubbing mode, while in someembodiments the non-current-time indicator may appear by way ofanimation such as translating into position or gradually becoming lesstransparent (e.g., fading in).

In some embodiments, a scrubbing time, such as one displayed on ascrubbing watch face or a scrubbing clock face, may be set in accordancewith user inputs, and may also be set to the current time (such that thescrubbing time and the current time may be the same time). In someembodiments, when a time-scrubbing mode is initially activated and auser input or instruction has not yet been received to set a scrubbingtime, the scrubbing time is automatically set to the current time as astarting point. In this way, in some embodiments, a non-current-timeindicator such as a scrubbing watch face or a scrubbing clock face maysometimes display the current time. In such instances, despite thenon-current-time indicator displaying a time that is the same as thecurrent time, a user may understand that the non-current-time indicatoris not an indication of the current time per se, but rather anindication that a scrubbing time is set to a time that is the same asthe current time.

In the depicted example of interface 5350 of FIG. 53B, time-scrubbingmode has been activated and, accordingly, scrubbing hands 5322 a and5322 b have been displayed in the same position that hands 5310 a and5310 b were displayed prior to the activation of time-scrubbing mode. Insome embodiments, scrubbing hands 5322 a and 5322 b are non-current-timeindicators configured to indicate a scrubbing time, although in theexample of interface 5350 of FIG. 53B, they are presently indicating ascrubbing time that is the same as the current time of 11:09.

In the depicted example of interface 5380 in FIG. 53E, time-scrubbingmode has been activated and, accordingly, digital clock face 5332 hasbeen displayed in the same position that digital clock face 5328 wasdisplayed prior to the activation of time-scrubbing mode. In someembodiments, digital clock face 5332 is a non-current-time indicatorconfigured to indicate a scrubbing time, although in the example ofinterface 5380 in FIG. 53E, it is presently indicating a scrubbing timethat is the same as the current time of 11:09.

In some embodiments, such as when a user executes multiple user inputsto scrub a scrubbing time forward and then backward, or backward andthen forward, to return the scrubbing time to zero, a non-current-timeindicator indicating the current time may also be responsivelydisplayed.

At block 5412, the device detects a first rotation of the rotatableinput mechanism. In some embodiments, a first rotation of the rotatableinput mechanism may comprise one or more rotations in one or moredirections, having one or more speeds, having one or more durations, andhaving one or more spacings relative to one another. In someembodiments, a first rotation of the rotatable input mechanism maycomprise a single rotation of a rotatable input mechanism in apredefined rotational direction. In some embodiments, a user may rotatea rotatable input mechanism in a first direction, and a device mayresponsively scrub a scrubbing time forward into the future (or, in someembodiments, backward into the past). In some embodiments, the firstrotation of a rotatable input mechanism may begin to be detected when atime-scrubbing mode is inactive, while in some embodiments it may beginto be detected while a time-scrubbing mode is already activated. In thedepicted examples of FIGS. 53B and 53E, rotational inputs 5320 a and5320 b are detected by device 5300 when a user rotates rotatable inputmechanism 5304 in a first direction.

In FIG. 54B, block 5402 is continued, such that the additional methodblocks are also performed at an electronic device with a display and arotatable input mechanism. In FIG. 54B, block 5414 follows from block5412.

At block 5414, blocks 5416 to 5442 (some of which are optional), shownin FIGS. 54B and 54C, are performed in response to detecting the firstrotation of the rotatable input mechanism. In discussing blocks 5416 to5442 below, the phrase “in response to detecting the first rotation ofthe rotatable input mechanism” may or may not be repeated for clarity.In some embodiments, method steps are performed in response to detectingrotation of a rotatable input mechanism, which may be the primary inputmechanism for driving functionality in a time-scrubbing mode. That is,in some embodiments, rotation of a rotatable input mechanism may be thecore manner in which a user scrubs time forward or scrubs time backward,and various elements of the user interface objects may react accordinglyto the user's rotational input commands.

At block 5416, in response to detecting the first rotation of therotatable input mechanism, the device displays a non-current-timeindicator indicating a first non-current time determined in accordancewith the first rotation. In some embodiments, the first non-current-timeindicator may be any of the non-current-time indicators described abovewith reference to block 5410, or may share some or all of thecharacteristics of the non-current-time indicators described above. Insome embodiments, in contrast to the non-current-time indicator in block5410, the non-current-time indicator displayed in block 5414 (which maybe a different non-current-time indicator or the same non-current-timeindicator) indicates a non-current time that is determined in accordancewith the first rotation. In some embodiments, the indicated non-currenttime is a scrubbing time, and the scrubbing time is determined inaccordance with a user's rotational scrubbing input.

In some embodiments, when the rotational input is detected before theactivation of time-scrubbing mode, a non-current-time indicator, such asa scrubbing-time digital clock face or scrubbing hands on an analogclock face, may begin to be displayed and display a user-selectedscrubbing time. In some embodiments, when the rotational input isdetected once a time-scrubbing mode has already been activated, then apreviously displayed non-current-time indicator may be modified todisplay a newly selected scrubbing time.

In some embodiments, a scrubbing time for a time-scrubbing mode may beselected in accordance with a characteristic of the rotational input,and the selected scrubbing time may be displayed by the non-current-timeindicator. In some embodiments, the non-current-time indicator maydisplay an animation of the indicator changing to the newly selectedscrubbing time, including any of the animation styles discussed abovewith reference to digital clock face 5317 and FIG. 53C. In someembodiments, an animation may include displaying clock hands (e.g., aminute hand and an hour hand) sweeping into new positions.

In some embodiments, a rotation of a rotational input mechanism in onedirection may cause scrubbing forward, while a rotation of therotational input mechanism in a direction substantially opposite to theone direction may cause scrubbing backward. In some embodiments, therate of scrubbing (forward or backward) may be proportionally related tothe rate of rotation; in some embodiments, the amount of time scrubbedmay be proportionally related to the distance (e.g., angular rotation)of rotation. In some embodiments, the scrubbing rate and amount of timescrubbed may simulate the effect of a watch crown, where clock hands arephysically connected to the crown by a series of gears, and accordinglythe movement of the hands follows a user's twisting of the crown,reflecting a rotation of the crown by way of a predefined gear ratio.(In some embodiments, the rate and distance of scrubbing of a digitalclock face may be the same as the rate and distance of scrubbing of adisplayed likeness of an analog clock face.)

In some embodiments, a device may provide different “gearings” fordifferent available faces. That is, a user may select between more thanone watch or clock interface, and, depending on the interface selected,the speed and distance of scrubbing in response to a given rotationalinput may vary. For example, in some embodiments, an interfacedisplaying (as a time indicator) a likeness of the globe may display onerotation of the globe (approximately 24 hours) in response to a firstrotation of the rotational input. Meanwhile, in some embodiments, aninterface displaying (as a time indicator) a likeness of the solarsystem may display one revolution of the Earth (approximately 365 days)in response to the same first rotation of the rotational input.Differences in the amount of time scrubbed in response to a givenrotational input may similarly be provided between other watch faces,such as an analog face like the one shown in interface 5340 in FIG. 53A,or a digital face such as the one shown in interface 5370 in FIG. 53D.

In some embodiments, the rate of time scrubbing and/or the amount oftime scrubbed in response to a rotational input may not have a fixedrelationship to the angular magnitude of the rotational input. That is,in some embodiments, a rotational input of a given angular magnitude mayresult in different amounts of time scrubbed, depending on various otherfactors. As discussed above, in some embodiments, different interfacesmay be associated with different default gearings. In some embodiments,a user may manually select different gearings, for example by executingan input on a displayed user interface object or by executing an inputby actuating a hardware button (e.g., executing one or more presses of arotatable and depressible input mechanism).

In some embodiments, a gearing may not be fixed, such that, during thecourse of an ongoing rotational input, the relative rate (e.g.,instantaneous rate) of time scrubbing as compared to the rate (e.g.,instantaneous rate) of rotation of the rotatable input mechanism may beincreased and/or decreased. For example, a variable gearing may beconfigured such that rotation below a threshold speed (e.g., angularrotation per second) causes time scrubbing at a first rate or a firstgearing, while rotation above the threshold speed causes time scrubbingat an accelerated rate or an accelerated fearing. In this way, when auser wishes to scrub by a large amount of time, the device may recognizetheir rapid rotation of the rotational input mechanism and accordinglyaccelerate the time scrubbing rate, helping the user to more easilyscrub by a large distance. In some embodiments, during an ongoingrotational input, if the speed of a rotational input drops below apredefined speed threshold after the time scrubbing rate has beenaccelerated, then the time scrubbing rate may be decelerated and/orreturned to its original rate; this deceleration may aid a user who hasused accelerated scrubbing to move the scrubbing time by a large amount,enabling the user to more precisely set the final desired scrubbing timeas the user begins to slow his rotational input. In some embodiments,gearing may be dynamically varied in accordance with any characteristicof a user input, such as a speed, a direction, a distance (e.g., angulardistance), and/or a pressure.

In some embodiments in which a time scrubbing speed is accelerated, itshould be noted that an animation of time scrubbing may be different foraccelerated scrubbing than for non-accelerated scrubbing. For example,in some embodiments, for non-accelerated scrubbing, a device may providea first animation of numbers on a digital clock face changing (with orwithout an accompanying animation such as a translation or a flippingeffect) or a first animation of a minute hand and an hour hand sweepingaround a clock face. Meanwhile, in some embodiments, for acceleratedscrubbing, a device may provide one or more different animations, suchas blurring numbers on a digital clock face to signify that they arebeing changed rapidly, or by providing an animation of a blurred minutehand (or hiding a minute hand altogether) in order to avoid the minutehand appearing to “jump” from one position to another on a displaywithout sweeping through intermediate positions. In some embodiments,such alternate animations for accelerated scrubbing may be provided aspart of an accelerated scrubbing mode, sometimes called a “turbo mode.”

In some embodiments, a scrubbing time may be set partially in accordancewith a user's input and partially in accordance with predefinedscrubbing times. For example, in some embodiments, predefined scrubbingtimes may be configured such that, when a user executes an input thatwould set a scrubbing time to a predefined range of times, the actualscrubbing time is set to a predefined time. For example, if a predefinedscrubbing time is 12:00 noon, and the user rotates a rotational inputmechanism an appropriate distance and speed to set the scrubbing time to11:58, then the scrubbing time may be rounded to 12:00 noon and set to12:00 noon. The range of scrubbing times that will “snap” to apredefined scrubbing time may be set to any suitable length of time,such as one minute, five minutes, 15 minutes, 30 minutes, one hour, sixhours, 12 hours, 24 hours, 2 days, one week, one month, one year, etc.In some embodiments, a device may snap to different predefined scrubbingtimes depending on what interface a user is using; for example, in aninterface featuring a likeness of the Earth or a representation of thesun, the device may be configured to “snap” to scrubbing times to timescorresponding to sunset, sunrise, or high noon. As another example, ininterfaces featuring a likeness of the solar system, the device may beconfigured to “snap” to scrubbing times corresponding to astronomicalevents such as planet alignments or eclipses.

In some embodiments, predefined scrubbing times may be determined inaccordance with user input. In some embodiments, a user may manually setpredefined scrubbing times, such as by setting “snap” times or selectinga “snap” interval. In some embodiments, predefined scrubbing times maybe set in accordance with data or information relating to one or moreuser interface objects or complications. For example, a device may beconfigured to round a scrubbing time to the time at which a calendarevent begins or ends. In some embodiments, a device may be configured toround a scrubbing time to times at which data for a complicationchanges, becomes available, or ceases to be available. In someembodiments, a device may be configured to slow or stop a scrubbing ratein accordance with a calendar event or other scheduled event beingreached while scrubbing forward or backward, and a device may beconfigured to snap or round a scrubbing time to a time corresponding tothe calendar event or scheduled event.

In the depicted example of interface 5360 in FIG. 53C, scrubbing hands5322 a and 5322 b have swept smoothly forward from their previousposition in interface 5350 in FIG. 53B, moving forward in time inaccordance with the speed and magnitude of user input 5320 a in FIG.53B, to indicate in user interface 5360 that the scrubbing time has beenset to the non-current time of 11:34, which is 25 minutes ahead of thecurrent time of 11:09. In the depicted example of interface 5390 in FIG.53F, the numerals in digital clock face 5332 have changed in accordancewith the speed and magnitude of user input 5320 b in FIG. 53C toindicate in user interface 5390 that the scrubbing time has been set tothe non-current time of 11:34, which is 25 minutes ahead of the currenttime of 11:09.

At block 5418, optionally, the first non-current time is a future time.In some embodiments, a non-current scrubbing time may be a time that isin the future as compared to the current time. In some embodiments, auser may scrub to a future time in a time-scrubbing mode by executing arotation of a rotatable input mechanism in a predefined direction. Apredefined direction of rotation for scrubbing into the future may besubstantially opposite to a predefined direction of rotation forscrubbing into the past. In the examples of interfaces 5360 and 5390 inFIGS. 53C and 53F, respectively, the scrubbing time is a future time of11:34, which is 25 minutes ahead of the current time of 11:09.

At block 5420, optionally, the first non-current time is a past time. Insome embodiments, a non-current scrubbing time may be a time that is inthe past as compared to the current time. In some embodiments, a usermay scrub to a past time in a time-scrubbing mode by executing arotation of a rotatable input mechanism in a predefined direction. Apredefined direction of rotation for scrubbing into the past may besubstantially opposite to a predefined direction of rotation forscrubbing into the future.

At block 5421, the non-current-time indicator is displayed at a locationat which the first current-time indicator was displayed before thedetection of the first rotation of the rotatable input mechanism. Insome embodiments, a non-current-time indicator, such as one that isnewly displayed upon the activation of time-scrubbing mode, may bedisplayed at a location at which a current-time indicator was previouslydisplayed before the activation of time-scrubbing mode. In someembodiments, the non-current-time indicator may appear in its displayedposition by way of any of the animations discussed above with referenceto digital clock face 5317 and FIG. 53C. In some embodiments, acurrent-time indicator such as a digital clock face may be animated astranslating out of the way, and a non-current-time indicator, such as adifferent digital clock face with numerals displayed in a differentcolor, may be animated as increasing in size as if appearing from thedistant z-axis and moving toward the viewer. In some embodiments, ascrubbing time indicator may replace the current-time indicator on thedisplay. In the example depicted in interfaces 5380 and 5390 of FIGS.53E and 53F, digital clock face 5332 is displayed at the same locationon display 5302 that digital clock face 5323 (which is reduced in sizeand translated to the upper corner upon the activation of time-scrubbingmode) was displayed in interface 5370 in FIG. 53D before the activationof time-scrubbing mode. In the example of interface 5350 in FIG. 53B,scrubbing hands 5322 a and 5322 b are displayed in the same position andsame orientation as hands 5310 a and 5310 b were previously displayed,though scrubbing hands 5322 a and 5322 b may be displayed in thedepicted position in response to a touch contact activatingtime-scrubbing mode; after a rotational input while in time-scrubbingmode, scrubbing hands 5322 a and 5322 b may be displayed at a differentorientation (e.g., indicating a different time) though in the samegeneral position (e.g., with the same center/anchor point) as hands 5310a and 5310 b were previously displayed, as depicted in interface 5360 ofFIG. 53C.

At block 5422, in response to detecting the first rotation of therotatable input mechanism, the device updates the first user interfaceobject to display information corresponding to the first non-currenttime, wherein the information corresponding to the first non-currenttime pertains to the first information source and is information otherthan a day, time, or date of the first non-current time. In someembodiments, when a user executes a rotational input as a command toscrub time forward or backward, one or more user interface objectsdisplayed on a user interface, such as one or more complications, may beupdated in accordance with the newly selected scrubbing time. In someembodiments, a user interface object or a complication may bepredetermined to correspond to a first information source, subjectmatter, and/or a first application, and scrubbing time forward orbackward will not change the information source, subject matter, orapplication to which a complication or user interface object pertains.For example, in some embodiments, when a complication is configured todisplay information pertaining to the weather obtained from a weatherapplication, scrubbing the time forward or backward may not change thatthe complication displays weather information obtained from a weatherapplication—rather, the change may be with respect to the time (ratherthan subject matter or information source) to which the displayedinformation pertains. That is, if the weather complication is configuredto display current weather information (e.g., the most up-to-datetemperature reading available) when a device is not in time-scrubbingmode, then scrubbing the time forward may cause the weather complicationto instead display forecasted or projected weather information, whilescrubbing the time backward may cause the device to display historicalweather information (or past projected weather information) in someembodiments.

In some embodiments, information may be considered to correspond to atime when the information is stored, linked, tagged, or associated withmetadata indicating that the information corresponds to that time. Forexample, a piece of information (such as a weather forecast) may bestored locally or remotely from the device, and may be associated with ametadata or other tag that indicates a future time to which the weatherforecast data corresponds (e.g., the time for the weather forecast). Insome embodiments, as a user scrubs forward or backward through time, thedevice may determine when to display the weather forecast data bycomparing the displayed scrubbing time to the time associated with thetag or metadata of the stored weather forecast (or other stored dataentry).

In some embodiments, a user interface object such as a complication maybe updated dynamically as a user scrubs time forward and/or scrubs timebackward. In some embodiments, information displayed by a complicationmay be updated with each displayed change to the non-current-timeindicator, or it may be updated in accordance with predefined periods ofscrubbing time (e.g., 5 minutes, 15 minutes, 1 hour, 1 day, etc.). Insome embodiments, information displayed by a complication may be updatedas frequently as new or different information from the currentlydisplayed information is available; for example, if a weather forecastpredicts a steady temperature for the next hour, and then an increase byone degree, then a complication displaying a weather temperature may notdisplay any change as the user scrubs through the first hour, then maydisplay the increased temperature when the scrubbing time reaches thetime at which the forecasted temperature changes.

In some embodiments, a user interface object such as a complication maybe updated by way of an animation, including any of the animationsdescribed above with reference to digital clock face 5317 and FIG. 53C.In some embodiments, when a numeral displayed by an animation ischanged, a sudden cut or a hard cut transition may be used. In someembodiments, when a change other than a single numeral being changed ismade to a complication, a transition animation may be displayed in whicha previous portion of (or all of) the complication is displayed astranslating upwards (e.g., as if being flipped and rotated upward abouta point of connection at the top of the complication, in the manner inwhich a page may be flipped upward on a notepad), shrinking in size,and/or fading away (e.g., becoming increasingly transparent in time);while a new portion of (or all of) the complication may be displayed asincreasing in size (as if translating in from the distant z-axis andmoving toward the viewer) and/or fading into view (e.g., becomingdecreasingly transparent in time).

In the example of interfaces 5360 and 5390 in FIGS. 53C and 53F,respectively, weather complication 5312 has been updated in accordancewith the time being scrubbed forward by 25 minutes to 11:34. Before thetime was scrubbed forward, weather complication 5312 displayed a currentweather temperature of 72°, while after the time has been scrubbedforward, weather complication 5312 has been updated to display aforecasted weather temperature of 73°, the forecasted weathertemperature being a forecast corresponding to the future scrubbing timeof 11:34.

At block 5424, optionally, the information corresponding to the firstnon-current time comprises projected data. In some embodiments, theinformation displayed by a user interface object or complication thathas been updated in a time-scrubbing mode may include projected orforecasted information, such as a weather forecast. In some embodiments,when forecasted or projected information (rather than known or scheduledinformation) is displayed, an indication (such as a visual symbol, adisplay stylization, etc.) may be provided to alert the user that theinformation is a forecast or a projection. In the example of interfaces5360 and 5390 in FIGS. 53C and 53F, respectively, the informationdisplayed by weather complication 5312 is projected data in the form ofa forecasted weather prediction for a future time.

In some embodiments, forecasted or projected information may pertain toa future scrubbing time, in that the prediction or forecast was madeabout a future time, such that the user is provided with a forecast or aprediction for the future. In some embodiments, forecasted or projectedinformation may pertain to a past time, in that the prediction orforecast was made at a past time, such that the user is provided with aprevious prediction or forecast.

At block 5426, optionally, the information corresponding to the firstnon-current time comprises a scheduled event. In some embodiments,information displayed by a complication may include calendar informationsuch as the name of a scheduled event, the time of a scheduled event,the place of a scheduled event, participants or invitees to a scheduledevent, or other information about a scheduled event. For example, acomplication may be configured to display information from a user'spersonal calendar; in some embodiments, the complication may display thename of a current calendar event, such as “Conference Call.” In someembodiments, the complication may display the name of a nearest upcomingcalendar event. In some embodiments, when a user scrubs forward orbackward in time, such a calendar complication may change to displayinformation corresponding to a calendar event scheduled for thescrubbing time, or to display information corresponding to a nearestupcoming calendar event with respect to the scrubbing time.

In some embodiments, when scrubbing into the future and/or the past, thedevice may determine what information to display in a different mannerthan the device determines what information to display for the currenttime when time-scrubbing mode is not activated. For example, if ameeting is scheduled for 12:00 noon, then a calendar complication may,in some embodiments, display information pertaining to the 12:00 noonmeeting starting at a time before 12:00 noon, such as 11:00 a.m. or 9:00a.m., or whenever a previous calendar event concludes. In this way, theuser may see the calendar event regarding the 12:00 noon meeting beforethe time of the meeting, and is less likely to forget about the meetingand be late. Thus, information may be displayed about the meeting for aperiod of time that extends beyond (e.g., before) the time of thecalendar event in the user's calendar. In some embodiments, the samething may not be true in time-scrubbing mode. For example, in someembodiments, when a user enters time-scrubbing mode, a calendarcomplication may suppress display of information pertaining to calendarevents when the scrubbing time is not set to a time for which thecalendar event is actually scheduled. Thus, for a noon meeting, despitethe device displaying the meeting, in some embodiments, outsidetime-scrubbing mode when the current time is 11:09, display of themeeting may be suppressed in time-scrubbing mode when the scrubbing timeis set to 11:09. In some embodiments, suppressing display of calendarevents in time-scrubbing mode when the scrubbing time is not set to atime for which the calendar event is actually scheduled may aid a user'squick comprehension of the time for which calendar events are scheduledwhen a user is scrubbing through time quickly. (Note that, in otherembodiments, time-scrubbing mode may display calendar information whenthe scrubbing time is not set to a time for which the calendar event isscheduled; in some such embodiments, the device may display a time forthe calendar event to aid a user's understanding of the time of thecalendar event as the user is scrubbing through time.)

At block 5428, optionally, the information corresponding to the firstnon-current time comprises historical data. In some embodiments,information displayed by a complication may include historicalinformation such as recorded data or other information. Recorded data orother information, in some embodiments, may include recordedmeasurements, figures, readings, statistics, or events. Recorded data orother information, in some embodiments, may include recorded forecastsor recorded predictions. Recorded data or other information, in someembodiments, may include any information regarding the previous state ofa device and/or of a user interface. In some embodiments, as a userscrubs through past times, a device may display historical data thatpertains to the past scrubbing time. In some embodiments, historicalinformation may pertain to a past scrubbing time in that the informationitself concerns the past scrubbing time (e.g., a weather temperaturereading at the time). In some embodiments, historical information maypertain to a past scrubbing time in that the information was recorded orcreated at the past scrubbing time (e.g., a weather forecast made at thepast scrubbing time).

Block 5430 optionally follows from blocks 5416-5420. At block 5430,optionally, in response to detecting the first rotation of the rotatableinput mechanism, the device updates the first user interface object toindicate a lack of information corresponding to the first non-currenttime. In some embodiments, as a user is scrubbing forward or backward intime in a time-scrubbing mode, a user interface object or complicationmay cease to be displayed to indicate that there is no information to bedisplayed corresponding to the selected scrubbing time. For example,when a user scrubs a stock-market complication to a future time, stockinformation may not be available for the future time; accordingly, thecomplication (or part of the complication) may cease to be displayed. Asimilar result could occur when a user scrubs so far forward in timethat reliable projection or forecast data is not available; for example,a user may scrub so far into the future that no weather forecast isavailable, and a weather complication could cease to be displayed. Asimilar result could occur when a user scrubs so far backward in timethat historical data is no longer available; for example, a device (oran information source to which the device has access) may only cache orotherwise store a limited amount of historical information, and when auser scrubs beyond that point, a complication may cease to be displayed.A similar result could also occur when a user scrubs to a time to whichno calendar data applies; for example, if a user scrubs to a time atwhich no events are scheduled on a calendar, then a device may cease todisplay a calendar complication.

In some embodiments, when a user scrubs to a time for which no relevantinformation is available for display by a complication, a complicationmay fade to a translucent appearance, may be displayed in a faded ormuted color scheme, or may be displayed in a grayed-out color scheme, toindicate to the user that no information is available for the selectedscrubbing time. In some such embodiments, the complication may continueto display, in the altered (e.g., faded or grayed-out) manner, theinformation that was most recently displayed by the complication. Thismay help the user to know that information pertaining to the selectedscrubbing time is not available, while allowing the user to remainoriented to, and aware of, the complication's presence.

In FIG. 54C, block 5402 is continued, such that the additional methodblocks are also performed at an electronic device with a display and arotatable input mechanism. In FIG. 54C, block 5414 is continued, suchthat blocks 5432-5442 (some of which are optional) are performed “inresponse to detecting the first rotation of the rotatable inputmechanism.” In discussing blocks 5432 to 5442 below, the phrase “inresponse to detecting the first rotation of the rotatable inputmechanism” may or may not be repeated for clarity.

Block 5432 follows from blocks 5422-5428, or optionally from block 5430.At block 5432, in response to detecting the first rotation of therotatable input mechanism, the device displays one of the firstcurrent-time indicator and a second current-time indicator. In someembodiments, block 5432 may optionally be performed in response todetecting a user input that activates a time-scrubbing mode, such as theuser input detected at block 5408. In some embodiments, when atime-scrubbing mode is activated (whether by a touch contact detected ona touch-sensitive surface or by a rotation of a rotatable inputmechanism), in addition to displaying a non-current-time indicatorindicating a scrubbing time, the device may also display a current-timeindicator. In some embodiments, the current-time indicator displayed intime-scrubbing mode may be the same current-time indicator that wasdisplayed before the activation of time-scrubbing mode, such as thecurrent-time indicator displayed at block 5404, such that the samecurrent-time indicator continues to be displayed. In some embodiments,the current-time indicator displayed in time-scrubbing mode may be asecond current-time indicator different from the current-time indicatorthat was displayed before the activation of time-scrubbing mode.

At block 5434, optionally, displaying the first current-time indicatorin response to detecting the first rotation comprises displaying thefirst current-time indicator with a modified visual appearance. In someembodiments, upon the activation of time-scrubbing mode, the visualappearance of the first current-time indicator may be altered in such away so as to signal to the user that time-scrubbing mode has beenactivated and to direct the user's focus to the non-current-timeindicator rather than the current-time indicator. For example, a size,shape, color, highlighting, and/or animation style of a current-timeindicator may be altered upon the activation of time-scrubbing mode.

In some embodiments, a current-time indicator may be displayed in afaded, muted, partially transparent, or grayed-out color scheme whiletime-scrubbing mode is active. In the depicted example of interface 5360in FIG. 53C, clock hands 5310 a and 5310 b are displayed in a grayed-outcolor scheme, as indicated by the hashing shown in the figure. Thisgrayed-out color scheme may signal to a user that time-scrubbing mode isactive, and may direct a user's attention to scrubbing hands 5322 a and5322 b instead, which may be displayed in a brighter or more noticeablecolor, such as green.

In the example of interface 5380 in FIG. 53E, digital clock face 5328may be displayed in green when time-scrubbing mode is activated, whereasit may have been displayed in white before time-scrubbing mode wasactivated. In some embodiments, displaying more user interface objects,including current-time indicators, in a bright color such as green maysignal to a user that the device is in a time-scrubbing mode ofoperation.

In some embodiments, a current-time indicator may be displayed in asmaller size than it was displayed before the activation of atime-scrubbing mode. In the depicted example of interface 5380 in FIG.53E, digital clock face 5328 has been translated to the top corner ofdisplay 5302 (as indicated by the diagonal arrow) and is displayed in asmaller size than the size at which it was displayed (in interface 5370in FIG. 53D) before the activation of time-scrubbing mode. The smallerdisplay size of the current-time indicator may signal to a user thattime-scrubbing mode is active, and may direct a user's attention todigital clock face 5332, which may be displayed in a larger size and maydisplay a scrubbing time.

At block 5436, optionally, displaying the first current-time indicatorin response to detecting the first rotation comprises displaying thefirst current-time indicator in a different position on the display thana position at which it was displayed prior to detecting the firstrotation. In some embodiments, upon the activation of time-scrubbingmode, a current-time indicator may cease to be displayed in one positionand instead be displayed in another position. The position at which thecurrent-time indicator is displayed during time-scrubbing mode may be aless prominent position than the prior position, such as a positioncloser to an edge or corner of the display. In the example of interface5390 in FIG. 53F, digital clock face 5328 is displayed at a differentposition than the position at which it was displayed (in interface 5370in FIG. 53D) prior to the activation of time-scrubbing mode, having beenmoved closer to the upper right-hand corner of display 5302.

At block 5438, optionally, displaying the first current-time indicatorin response to detecting the first rotation comprises animating thefirst current-time indicator from its initial position to the differentposition on the display. In some embodiments, the animation may comprisethe indicator fading away (e.g., becoming more transparent) from its oldposition and/or fading into (e.g., becoming less transparent) its newposition. In some embodiments, the animation may include translating theobject across the display. In some embodiments, the animation mayinclude displaying the object increasing or decreasing in size. In someembodiments, the animation may include any of the animations describedabove with respect to digital clock face 5317 and FIG. 53C or withrespect to block 5422. In some embodiments, the current-time indicatormay suddenly cease to be displayed at its initial position andimmediately begin to be displayed at the different position.

At block 5440, optionally, in response to detecting the first rotationof the rotatable input mechanism, the device displays a time differenceindicator indicating a time difference between the current time and thefirst non-current time. In some embodiments, a time difference indicatormay be any user interface object that indicates a difference between onetime and another time, such as the difference between a current time anda scrubbing time. In some embodiments, a time difference indicator mayindicate a number of seconds, minutes, hours, days, weeks, months,years, etc. In some embodiments, a time difference indicator mayindicate whether a scrubbing time is in the future or in the pastrelative to a current time. In some embodiments, a time differenceindicator is automatically displayed upon activation of time-scrubbingmode. In some embodiments, explicitly displaying the difference betweenthe scrubbing time and the current time may help a user to more easilyunderstand and contextualize how far away from the current time thescrubbing time (and the corresponding information displayed in thecomplications) is. In the example of interfaces 5350 and 5360 in FIGS.53B and 53C, respectively, time difference indicator 5318 uses numeralsto indicate the number of minutes difference between the current timeand the scrubbing time, which is zero minutes in FIG. 53B and 25 minutesin FIG. 53C. In the example depicted, time difference indicator 5318uses a “+” symbol to indicate that the scrubbing time is in the futureas compared to the current time (and defaults to using a “+” symbol whenthe scrubbing time is equal to the current time). In some embodiments,if the scrubbing time is in the past as compared to the current time,then time difference indicator 5318 may display a “−” symbol to indicatethat the scrubbing time is a past time.

In some embodiments, when time-scrubbing mode is activated, elementspreviously displayed on the display may be removed from the display. Forexample, in some embodiments, complications or other user interfaceobjects displayed at a portion of the display where a time differenceindicator is displayed may be removed from the display (e.g., the devicemay cease to display them) during time-scrubbing mode. In someembodiments, the same may be true of interface objects or complicationsthat are displayed at a location on the display where a current-timeindicator (or an accompanying object such as the displayed word “NOW”)is displayed when time-scrubbing mode is active. In some embodiments,complications may be removed from the display upon the activation oftime-scrubbing mode without regard for whether any other object will bedisplayed at the same location on the display during time-scrubbingmode. In some embodiments, when a current-time indicator or atime-difference indicator is displayed at or moved to a location of adisplay at which numbers on a likeness of an analog clock face weredisplayed, the numbers on the likeness of the analog clock face may behidden; for example, if a current-time indicator or time-differenceindicator is displayed near the bottom of a clock interface in atime-scrubbing mode, then the numbers “5,” “6,” and “7” may be hidden onthe clock face. In some embodiments, dials or sub-dials displayed in adevice interface (such as any dial described elsewhere in thisdisclosure) may cease to be displayed upon the activation oftime-scrubbing mode when a time-difference indicator or a current-timeindicator is displayed at a portion of the display at which the dial orsub-dial was previously displayed.

In some embodiments, user interface elements displayed before theactivation of a time-scrubbing mode may change in size or appearance inorder to make room for the display of a time-difference indicator or acurrent-time indicator in time-scrubbing mode. For example, in someembodiments, previously-displayed tick marks may be replaced by oranimated as transitioning into dots, which may be smaller in size and/ormay have more empty space between them on the display. In someembodiments, any suitable user interface object may shrink in sizeand/or change locations on the display upon the activation oftime-scrubbing mode, including to create space on the display for thedisplay of a time-difference indicator and/or a current-time indicatoror associated user interface objects.

In FIG. 54D, block 5402 is continued, such that the additional methodblocks are also performed at an electronic device with a display and arotatable input mechanism.

Blocks 5442, 5444-5446, and 5448 each follow, optionally, from blocks5414-5440.

At block 5442, optionally, in response to a passage of time, the deviceupdates the non-current-time indicator to indicate a second non-currenttime in accordance with the passage of time, such that a time differencebetween the current time and a presently indicated non-current timeremains fixed. In some embodiments, as time passes, the current time isaccordingly updated to keep time. Additionally to updating the currenttime, the device, in some embodiments, also updates a non-current time,such as a scrubbing time for time-scrubbing mode, in accordance with thepassage of time. In this way, in some embodiments, once a user has set ascrubbing time, the difference between the scrubbing time and thecurrent time may remain fixed even as time passes. Thus, in someembodiments, when a scrubbing time is set to the future, the currenttime will not “catch up” to the scrubbing time, because the scrubbingtime will advance in time in parallel to the current time.

In some embodiments, as the scrubbing time is advanced in accordancewith the passage of time, complications and other user interface objectsmay be accordingly updated, in accordance with any of the methodsexplained above, to reflect the newly updated scrubbing time. Thus, acomplication in time-scrubbing mode may be updated, in some embodiments,both in accordance with the scrubbing time being altered by user inputand in accordance with the scrubbing time being altered by the passageof time.

At block 5444, optionally, while displaying the updated first userinterface object displaying information corresponding to the firstnon-current time, the device detects a second touch contact at alocation corresponding to the updated first user interface object, andin response to detecting the second touch contact, displays a userinterface corresponding to the first user interface object. The touchcontact detected may be a single-touch input, a multi-touch input, asingle-tap input, and/or a multi-tap input detected by touch- and/orpressure-sensitive elements in any touch- and/or pressure-sensitivesurface, including a touch-screen. In some embodiments, complications orother user interface objects that are updated in accordance with ascrubbing time in time-scrubbing mode may be selectable affordances,such that if a device detects an input at a location corresponding tothe complication, then an interface or application associated with thecomplication may be accessed. For example, a user may tap on a weathercomplication, in some embodiments, such as weather complication 5312, tocause an associated weather application to be opened. In anotherexample, a user may tap on a stock-market complication such asstock-market complication 5314, and, in some embodiments, a stock-marketapplication may be opened. In the depicted example of FIGS. 53C and 53F,user inputs 5336 a and 5336 b are detected on display 5302 at a locationat which weather complication 5312 is displayed; in some embodiments, inresponse to detecting user input 5336 a or 5336 b, a weather applicationmay be accessed and a weather interface may be displayed.

At block 5446, optionally, the user interface displayed in accordancewith the detection of a second touch contact at a location correspondingto the updated first user interface object corresponds to the firstnon-current time. In some embodiments, the functionality of tapping orotherwise selecting complications or other user interface objects mayvary in accordance with the displayed scrubbing time, such that adifferent application or interface may be provided depending on what thescrubbing time is set to at the moment of the user's selection. Forexample, in response to a user tapping a weather complication when thedevice is scrubbed to a past time, an interface of a weather applicationshowing historical weather data for the scrubbed-to past time may bedisplayed; in response to a user tapping a weather complication when thedevice is scrubbed to a future time, an interface of a weatherapplication showing forecasted weather for the scrubbed-to future timemay be displayed. In another example, in response to a user tapping acalendar complication, a calendar event that is scheduled for thescrubbed-to time may be opened, and an interface for that specific eventmay be displayed. In the depicted example of FIGS. 53C and 53F, inresponse to detecting user input 5336 a or 5336 b, device 5300 mayprovide an interface corresponding to forecasted weather informationassociated with the scrubbing time of 11:34 in some embodiments.

In some embodiments, a displayed complication may correspond to aninterface of the device that is configured to display a likeness of theEarth, the moon, and/or the solar system. In some embodiments, if a userscrubs time forward or backward on a scrubbing interface that containssuch a complication, and then taps the complication to select it, then acorresponding Earth, moon, and/or solar system interface may bedisplayed, wherein the Earth, moon, and/or solar system interface isitself scrubbed forward to the scrubbing time of the previous interface.In some embodiments, a user may select complications corresponding toEarth, moon, and/or solar system interfaces to cause an animation to bedisplayed of the interface “flying” (e.g., smoothly zooming and panning)between views of the Earth, views of the moon, and/or views of the solarsystem. As the user flies between these various interfaces, in someembodiments, time scrubbing may be maintained, and the scrubbing timemay be reflected in the complications displayed in each interface and/orin the displayed likenesses of the Earth, the moon, and/or the solarsystem.

At block 5448, optionally, the device detects a third touch contact at alocation corresponding to the first current-time indicator, and inresponse to detecting the third touch contact, ceases to display thenon-current-time indicator and updates the first user interface objectto display information corresponding to the current time. The touchcontact detected may be a single-touch input, a multi-touch input, asingle-tap input, and/or a multi-tap input detected by touch- and/orpressure-sensitive elements in any touch- and/or pressure-sensitivesurface, including a touch-screen. In some embodiments, when a user tapson the current-time indicator, the device may responsively exittime-scrubbing mode. Upon exiting time-scrubbing mode, in someembodiments, the device may cease to display the scrubbing time. Uponexiting time-scrubbing mode, in some embodiments, display of the currenttime may return to an original visual appearance (e.g., position, size,color, style, etc.) that was displayed before time-scrubbing mode wasactivated. Upon exiting time-scrubbing mode, in some embodiments,complications or other user interface object that were updated, inaccordance with any of the above methods, to correspond to a scrubbingtime, may be again updated to correspond to the current time. In someembodiments, this may involve returning to their original appearancefrom before time-scrubbing mode was activated, while in some embodimentsit may involve displaying new and/or different information (such asinformation corresponding to a new current time that is different fromwhen time-scrubbing mode was activated, or information that is newlyavailable or has been updated since time-scrubbing mode was activated).The displayed complications or user interface objects may be updated,upon deactivating time-scrubbing mode, in accordance with any of theanimations discussed above with reference to digital clock face 5317 inFIG. 53C. In the depicted example of FIGS. 53C and 53F, touch contacts5324 a and 5334 a are each detected at a location on display 5302 atwhich a current-time indicator is displayed; in response to detectingeither input, device 5300 may cause time-scrubbing mode to bedeactivated, and the displayed time indicators and complications may beaccordingly updated. In the depicted example, if no information haschanged and the time has not changed since the activation oftime-scrubbing mode, exiting time-scrubbing mode in FIGS. 53C and 53Fmay cause the display, respectively, of interface 5340 in FIG. 53A andof interface 5370 in FIG. 53C.

In some embodiments, other user inputs may be operable to cause thedevice to exit a time-scrubbing mode. In some embodiments, alternateuser inputs that may cause a device to exit a time-scrubbing mode mayinclude a depression of a rotatable and depressible input mechanism,such as user inputs 5324 b and 5334 b in FIGS. 53C and 53F,respectively. Allowing a user to exit a time-scrubbing mode bydepressing a rotatable and depressible input mechanism may increase theease of scrubbing time forward or backward and then easily exitingtime-scrubbing mode when a user is finished with time-scrubbing mode, ascommands to execute both functions can be entered with a single inputmechanism. In some embodiments, a device may exit a time-scrubbing modeafter a predefined period of time of inactivity, such as when a devicetimes out and a display is darkened.

At block 5450, optionally, the device detects a second rotation of therotatable input mechanism, and, in response to detecting the secondrotation of the rotatable input mechanism, the device updates thenon-current-time indicator to indicate a third non-current time,determined in accordance with the second rotation, and updates the firstuser interface object to display information corresponding to the thirdnon-current time, wherein the information corresponding to the thirdnon-current time pertains to the first information source and isinformation other than a day, a time, or a date of the first non-currenttime; and displays one of the first current-time indicator and thesecond current-time indicator. In some embodiments, after detecting afirst rotation and setting a first scrubbing time, as described above, adevice may then detect another rotation of the same rotational inputmechanism, and may set another scrubbing time in accordance with thesecond rotation. The device may set a second scrubbing time inaccordance with any of the methods described above, and may update thedisplayed user interface object and complications to correspond to thesecond scrubbing time in accordance with any of the methods describedabove. In some embodiments, a user may scrub forward or backward intime, pause, and then scrub forward or backward in time again, with orwithout leaving time-scrubbing mode. In some embodiments, displayedcomplications may be dynamically updated throughout the process toalways reflect the displayed scrubbing time as the user scrubs, pauses,and then scrubs again. In some embodiments, this process may be whollyor partially repeated or iterated any number of times.

In FIG. 54E, block 5402 is continued, such that the additional methodblocks are also performed at an electronic device with a display and arotatable input mechanism.

Blocks 5452 and 5454 follow, optionally, from blocks 5414-5440.

At block 5452, optionally, the device displays a second user interfaceobject configured to display second information corresponding to thecurrent time, wherein the second information corresponding to thecurrent time pertains to a second information source and is informationother than a day, time, or date of the current time; and, in response todetecting the first rotation of the rotatable input mechanism: updatesthe second user interface object to display second informationcorresponding to the first non-current time, wherein the secondinformation corresponding to the first non-current time pertains to thesecond information source and is information other than a day, time, ordate of the first non-current time.

At block 5454, optionally, the first and second information sources areseparate applications.

In some embodiments, a device may display more than one complication orother user interface object, wherein the complications or other userinterface objects pertain to separate subject matters, separateinformation sources, or separate applications of the device. Forexample, in some embodiments, an interface of a device such as a watchface interface or a home screen interface may display two distinctcomplications, each complication being associated with a distinctapplication of the device and each complication drawing information fromthe respective associated application and displaying the information onthe interface. In the depicted example of FIG. 53A, weather complication5312 and stock-market complication 5314 are distinct complications thatmay each be associated with a distinct information source and/orapplication (e.g., a weather application and a stock-marketcomplication, respectively).

In some embodiments, when a user scrubs time forward or backward in anyof the manners described above, not just one but both (and, in someembodiments, more than two) of the displayed complications or other userinterface objects are simultaneously updated in accordance with the timescrubbing. A second displayed complication or user interface object (inaddition to a third, fourth, etc.) may be updated in accordance withscrubbing by any of the methods described above. In some embodiments,all of the complications displayed on an interface may be simultaneouslyupdated in accordance with the displayed non-current time as a userscrubs through time. This may be advantageous because, in someembodiments, a user may be able to observe past information and/orfuture information of more than one information source or of more thanone application without having to separately open each application; thismay allow a user to observe and recognize contextual relationshipsbetween temporally-related data provided by different applications ordifferent information sources by being able to see information from allapplications at once, the information displayed all corresponding to thesame past time or to the same future time.

In the depicted example of FIG. 53C, in response to the user scrubbingforward in time by 25 minutes to a scrubbing time of 11:34, weathercomplication 5312 has been updated in accordance with the scrubbing timeto display a forecasted weather temperature of 73° for the scrubbingtime of 11:34. At the same time, stock-market complication 5314 has beenupdated by being removed from interface 5360, in accordance with thefact that no information is available from the stock-market applicationor information source associated with stock-market complication 5314.(In some embodiments, a second complication having access toinformation, from an associated application or information source,corresponding to the scrubbing time of 11:34, could display theinformation alongside the information displayed by weather complication5312.) Thus, in some embodiments, in order to view future information(or to be informed of a lack of future information) from the distinctand separate applications that are associated with complications 5312and 5314, a user may not need to separately access each application orseparately instruct each application to access and/or display futureinformation; rather, simply by scrubbing to a future time, bothcomplications may be caused to simultaneously access and display futureinformation corresponding to the selected scrubbing time.

It should be understood that the particular order in which theoperations in FIG. 54 have been described is merely exemplary and is notintended to indicate that the described order is the only order in whichthe operations could be performed. One of ordinary skill in the artwould recognize various ways to reorder the operations described herein.

Note that details of the processes described above with respect tomethod 5400 (e.g., FIG. 54) are also applicable in an analogous mannerto the methods and techniques described elsewhere in this application.For example, other methods described in this application may include oneor more of the characteristics of method 5400. For example, the devices,hardware elements, inputs, interfaces, modes of operation, faces, timeindicators, and complications described above with respect to method5400 may share one or more of the characteristics of the devices,hardware elements, inputs, interfaces, modes of operation, faces, timeindicators, and complications described elsewhere in this applicationwith respect to other methods. Moreover, the techniques described abovewith respect to method 5400 may be used in combination with any of theinterfaces, faces, or complications described elsewhere in thisapplication. For brevity, these details are not repeated elsewhere inthis application.

In accordance with some embodiments, FIG. 55 shows an exemplaryfunctional block diagram of an electronic device 5500 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 5500 are configured to perform the techniques described above.The functional blocks of the device 5500 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 55 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 55, electronic device 5500 includes a display unit 5502configured to display a graphic user interface including complications,current-time indicators, and non-current-time indicators; electronicdevice 5500 further includes a rotatable input mechanism unit 5504configured to receive rotational inputs. Optionally, device 5500 alsoincludes a touch-sensitive surface unit 5506 configured to receivecontacts. Device 5500 further includes processing unit 5508 coupled todisplay unit 5502, rotatable input mechanism unit 5504, and, optionally,touch-sensitive surface unit 5506. Processing unit 5508 contains displayenabling unit 5510, detecting unit 5512, and updating unit 5514.Optionally, processing unit 5508 further ceasing display enabling unit5516.

Processing unit 5512 is configured to: enable display (e.g., withdisplay enabling unit 5510) on display unit 5502 of a first current-timeindicator indicating a current time;

enable display (e.g., with display enabling unit 5510) on display unit5502 of a first user interface object configured to display informationcorresponding to the current time, wherein the information correspondingto the current time pertains to a first information source and isinformation other than a day, time, or date of the current time; detect(e.g., with detecting unit 5512) a first rotation of rotatable inputmechanism unit 5504; in response to detecting the first rotation ofrotatable input mechanism unit 5504: enable display (e.g., with displayenabling unit 5510) on display unit 5502 of a non-current-time indicatorindicating a first non-current time determined in accordance with thefirst rotation; update (e.g., with updating unit 5514) the first userinterface object to display information corresponding to the firstnon-current time, wherein the information corresponding to the firstnon-current time pertains to the first information source and isinformation other than a day, time, or date of the first non-currenttime; and enable display (e.g., with display enabling unit 5510) ondisplay unit 5502 of one of the first current-time indicator and asecond current-time indicator.

In some embodiments, processing unit 5508 is further configured to: inresponse to detecting the first rotation of the rotatable inputmechanism unit 5504: update (e.g., with updating unit 5514) the firstuser interface object to indicate a lack of information corresponding tothe first non-current time.

In some embodiments, the first non-current time is a future time.

In some embodiments, the information corresponding to the firstnon-current time comprises projected data.

In some embodiments, the information corresponding to the firstnon-current time comprises a scheduled event.

In some embodiments, the first non-current time is a past time.

In some embodiments, the information corresponding to the firstnon-current time comprises historical data.

In some embodiments, enabling display (e.g., with display enabling unit5510) on display unit 5502 of the first current-time indicator inresponse to detecting the first rotation comprises enabling display ondisplay unit 5502 of the first current-time indicator with a modifiedvisual appearance.

In some embodiments, enabling display (e.g., with display enabling unit5510) on display unit 5502 of the first current-time indicator inresponse to detecting the first rotation comprises enabling display ondisplay unit 5502 of the first current-time indicator in a differentposition on the display than a position at which it was displayed priorto detecting the first rotation.

In some embodiments, enabling display (e.g., with display enabling unit5510) on display unit 5502 of the first current-time indicator inresponse to detecting the first rotation comprises animating the firstcurrent-time indicator from its initial position to the differentposition on the display.

In some embodiments, the non-current-time indicator is displayed at alocation at which the first current-time indicator was displayed beforethe detection of the first rotation of rotatable input mechanism unit5504.

In some embodiments, processing unit 5508 is further configured to: inresponse to detecting the first rotation of rotatable input mechanismunit 5504, enable display (e.g., with display enabling unit 5510) ondisplay unit 5502 of a time difference indicator indicating a timedifference between the current time and the first non-current time.

In some embodiments, processing unit 5508 is further configured to:before detecting the first rotation of rotatable input mechanism unit5504, detect (e.g., with detecting unit 5512) a first touch contact at alocation corresponding to the first current-time indicator; and inresponse to detecting the first touch contact: enable display (e.g.,with display enabling unit 5510) on display unit 5502 of thenon-current-time indicator indicating the current time.

In some embodiments, processing unit 5508 is further configured to: inresponse to a passage of time, update (e.g., with updating unit 5514)the non-current-time indicator to indicate a second non-current time inaccordance with the passage of time, such that a time difference betweenthe current time and a presently indicated non-current time remainsfixed.

In some embodiments, processing unit 5508 is further configured to:while enabling display on display unit 5502 of the updated first userinterface object displaying information corresponding to the firstnon-current time, detect (e.g., with detecting unit 5512) a second touchcontact at a location corresponding to the updated first user interfaceobject; and in response to detecting the second touch contact, enabledisplay (e.g., with display enabling unit 5510) on display unit 5502 ofa user interface corresponding to the first user interface object.

In some embodiments, the user interface corresponds to the firstnon-current time.

In some embodiments, processing unit 5508 is further configured to:after detecting the first rotation of rotatable input mechanism unit5504, detect (e.g., with detecting unit 5512) a third touch contact at alocation corresponding to the first current-time indicator; and inresponse to detecting the third touch contact: cease to enable display(e.g., with ceasing display enabling unit 5518) on display unit 5502 ofthe non-current-time indicator; and update (e.g., with updating unit5514) the first user interface object to display informationcorresponding to the current time.

In some embodiments, processing unit 5508 is further configured to:detect (e.g., with detecting unit 5512) a second rotation of rotatableinput mechanism unit 5504; in response to detecting the second rotationof rotatable input mechanism unit 5504: update (e.g., with updating unit5514) the non-current-time indicator to indicate a third non-currenttime determined in accordance with the second rotation; update (e.g.,with updating unit 5514) the first user interface object to displayinformation corresponding to the third non-current time, wherein theinformation corresponding to the third non-current time pertains to thefirst information source and is information other than a day, time, ordate of the first non-current time; and enable display (e.g., withdisplay enabling unit 5510) on display unit 5502 of one of the firstcurrent-time indicator and the second current-time indicator.

In some embodiments, processing unit 5508 is further configured to:enable display (e.g., with display enabling unit 5510) on display unit5502 of a second user interface object configured to display secondinformation corresponding to the current time, wherein the secondinformation corresponding to the current time pertains to a secondinformation source and is information other than a day, time, or date ofthe current time; and in response to detecting the first rotation ofrotatable input mechanism unit 5504: update (e.g., with updating unit5514) the second user interface object to display second informationcorresponding to the first non-current time, wherein the secondinformation corresponding to the first non-current time pertains to thesecond information source and is information other than a day, time, ordate of the first non-current time.

In some embodiments, the first and second information sources areseparate applications.

The operations described above with reference to FIGS. 54A-54E are,optionally, implemented by components depicted in FIG. 1A, 1B, 2, 3, 4A,4B, 5A, 5B, 53A, 53B or 55. For example, displaying operations 5404,5406, 5416, and 5432; detecting operation 5412; and updating operation5422 may be implemented by event sorter 170, event recognizer 180, andevent handler 190. Event monitor 171 in event sorter 170 detects acontact on touch-sensitive display 112, and event dispatcher module 174delivers the event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface corresponds to apredefined event or sub event, such as activation of an affordance on auser interface. When a respective predefined event or sub-event isdetected, event recognizer 180 activates an event handler 190 associatedwith the detection of the event or sub-event. Event handler 190 mayutilize or call data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A, 1B, 2, 3, 4A, 4B, 5A, 5B.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

FIGS. 56A-56I show exemplary context-specific user interfaces that maybe operated on device 5600. Device 5600 may be device 100, 300, or 500in some embodiments. In some embodiments, the electronic device has atouch-sensitive display (e.g., touchscreen 504).

Device 5600 displays user interface screen 5602 which includes aplurality of affordances representing various event data from two ormore distinct applications (e.g., email, calendar, notification). Eventdata include any data that are associated with a time or a time period,such as, non-exclusively, meeting data from a calendar application,messaging data from a messaging application, email data from an emailapplication, notification data for certain events from a notificationapplication. Affordances representing event data from the differentapplications are arranged to serve as an immediate notification to theuser of times and schedules associated with the event data.

In some embodiments, as shown in FIG. 56A, user interface screen 5602includes a timeline (e.g., 5606) with a plurality of columns (e.g.,5606-a) and rows (e.g., 5606-b). The plurality of columns 5606-arepresent applications (e.g., a calendar application, an emailapplication, a notification application, etc.), and the plurality ofrows 5606-b represent times (e.g., 9 am, 10 am, 11 am, 12 pm, 1 pm, 2pm, 3 pm, etc.). By placing affordances representing events atappropriate columns and rows, the timeline can easily and efficientlyinform the user of the upcoming events and their associated times andapplications.

In FIG. 56A, each column includes an affordance (e.g., 5603, 5604, or5605) that represents an application. For example, the first columnincludes affordance 5603 representing a calendar application. The secondcolumn includes affordance 5604 representing an email application. Thethird column includes affordance 5605 representing a notificationapplication. There are additional columns to the right and/or left ofthe displayed portion of timeline 5606 representing further applicationsthan the displayed applications. Further, a part of the fourth column isdisplayed in user interfaces screen 5602, suggesting that there is atleast one additional column to the left of the displayed portion in thetimeline.

Similarly, each row includes an affordance (e.g., number 5607, or othergraphics or texts) that represents a time or a time period. The firstrow is displayed between affordance 5607 representing 9:00 am andaffordance representing 10 am, thus representing a one-hour time blockfrom 9 am to 10 am. Subsequent rows are displayed between affordancesrepresenting the later hours to represent different time blocks at aninterval of a one-hour time period (e.g., second row representing aone-hour time block from 10 am to 11 am, third row representing from 11am to 12 pm, etc.). There may be additional rows below and above thedisplayed portion of the timeline 5606 representing times beyond thedisplayed hours (such as, for example, 8 am, 7 am, 6 am, etc., above thedisplayed portion, and 4 pm, 5 pm, 6 pm, 7 pm etc., below the displayedportion).

In FIG. 56A, representations of event data obtained from the two or moredifferent applications (e.g., affordances 5609, 5610, 5611, 5612) arearranged relative to each other according to their associated times andapplications. In the illustrated example, affordance 5609 represents ameeting event from a calendar application, which is scheduled from 9 amto 10 am. Thus, affordance 5609 is displayed at a first columnindicating the calendar application (with affordance 5603) and at afirst row representing an hour block from 9 am to 10 am. Affordances foradditional meeting(s) from the calendar application (e.g., affordancesfor “Meeting 2” and “Meeting 3”) are arranged in the first column and atappropriate rows representing the respective times associated with thoseadditional meeting data. For example, the illustrated user interfacescreen 5602 notifies the user that “Meeting 2” from the calendarapplication is scheduled for an hour from 12 pm to 1 pm, and “Meeting 3”from the calendar application is scheduled for half an hour from 2:30 pmto 3 pm. As such, an appropriate arrangement of the affordances in agrid timeline may immediately notify the user of any upcoming eventsalong with the nature of those events as well as the times scheduled foreach event.

Similarly, in the illustrated example, affordance 5610 represents emaildata obtained from an email application which is associated with time10:30 am (e.g., a time at which the email was received). Thus,affordance 5610 is displayed at a second column indicating the emailapplication (with affordance 5604) and at a row indicating 10:30 am.Although the email data is associated with a specific time point, ratherthan a time block, the affordance representing the email data may bedisplayed, as shown in the illustrated example, to occupy a time block(e.g., 30 minutes, 15 minutes) starting from the specific time pointassociated with the email data. Affordances for additional email datafrom the email application are arranged in the second column and atappropriate rows representing the respective times associated with thoseadditional email data. For example, the illustrated user interfacescreen 5602 notifies the user that “Email 2” from the email applicationwas received at 1:00 pm.

Further, affordance 5611 represents notification data for a particularevent (e.g., a software update, a backup schedule, etc.) obtained from anotification application where the event is scheduled to run at 10:30am. The event represented by the notification data may be,non-exclusively, a software update schedule, a backup schedule, or anyother device schedules that may warrant a forewarning. In theillustrated example, affordance 5611 representing the notification datais displayed at a third column indicating the notification application(with affordance 5605) and at a row indicating a 30-minute time blockfrom 10:30 am. The notification data may be associated with a specifictime point (e.g., a time at which the associated event is scheduled tostart) or a time block (e.g., if the device has information regarding anestimated duration for which the associated event is scheduled to run,etc.). Affordances for additional notification data from thenotification application are arranged in the third column and atappropriate rows representing the respective times associated with theadditional notification data. For example, the illustrated userinterface screen 5602 notifies the user that “Notification 2” (e.g., foranother event such as a software update, a backup, etc.) from thenotification application is scheduled at 12:00 pm.

Further, in some embodiments, as shown in FIG. 56A, the user interface(e.g., timeline 506) provides the user with the ability to correlate andcross-reference information from different applications, by time. Forexample, one can see that Email 2 was received right after Meeting 2 andmay be related to the meeting.

In some embodiments, as shown in FIG. 56A, user interface screen 5602displays a portion of the user interface (e.g., timeline 5606) due tolimitations on the display size. The display of a portion of the fourthcolumn with representation 5612 suggests that there is at least oneadditional column representing an additional application to the left ofthe displayed portion of the user interface (e.g., timeline 5606). Assuch, in cases where the user interface screen 5602 displays a portionsmaller than the entirety of the user interface (e.g., timeline 5606), auser can scroll the user interface to navigate through differentportions (e.g., replace the current portion with display of a differentportion). For example, a user may provide an input to scroll the userinterface using a finger gesture (e.g., a swipe gesture) on a touchsensitive display of device 5600, a stylus gesture, a hand motion, or arotatable input mechanism (e.g., 5601) of device 5600, etc.

In FIG. 56A, a user provides an input corresponding to a request toscroll the user interface (e.g., timeline 5606) in a rightwarddirection, by making a rightward finger swipe gesture (e.g., 5613 inFIG. 56A) on a touch-sensitive display of device 5600. In response todetecting the finger swipe gesture 5613, device 5600 scrolls the userinterface (e.g., timeline 5606) such that the portion shown in the userinterface screen 5602 is replaced with the portion shown in 5602 b inFIG. 56B.

In FIG. 56B, user interface screen 5602 b displays a different portionof the user interface (e.g., timeline 5606) that includes a full view ofthe fourth column (which was only partially displayed in the previousportion shown in FIG. 56A). The fourth column includes representation of“X” application (e.g., affordance 5615). The “X” application is,optionally, a second calendar application, a second email application, amessaging application, a health-related application, a game application,or any other application that can create an event or provide dataassociated with a time or a time period. Event data from the “X”application are represented with affordances (e.g., affordance 5612 for“Event 1” and affordance for “Event 2”) which are arranged in the fourthcolumn and at appropriate rows according to the respective timesassociated with the event data.

Optionally, a user is allowed to modify settings associated with theuser interface (e.g., timeline 5606) to remove, add or changeapplications from which device 5600 obtains the event data and toultimate organize and display on the user interface (e.g., timeline).For example, a user may change the settings so that device 5600 obtainsevent data only from the default email application and default calendarapplication to simplify the timeline, etc. Further, a user may modifythe settings to rearrange the order of the applications represented bythe columns of the timeline. For example, a user may rearrange the orderof the applications so that the first column (the leftmost column inFIG. 56A) represents an email application not a calendar application,etc.

Further, device 5600 may obtain event data from various applications notonly running on device 5600 but also running on different devices thatare connected to device 5600 via a communication medium (e.g.,Bluetooth, Wi-Fi, cellular data network, mobile satellite network,wireless sensor network, wired or wireless communication medium). Forexample, a wearable device 5600 is connected to a second device (e.g., amobile phone, a tablet, a computer) via a wireless medium and obtainsevent data from applications on the second device. In some embodiments,device 5600 may download event data from a cloud storage connected to aplurality of different devices.

Moreover, a user is further allowed to modify the settings associatedwith the user interface (e.g., timeline 5606) to selectively obtain theevent data from the applications (e.g., device 5600 is set to obtainonly the event data that meet certain criteria from a certainapplication). For example, a user adjusts the setting to obtain only theevent data from the notification application that meet prioritycriteria, which are met, for example, when the associated events (e.g.,software update, backup, etc.) are scheduled to start within 24 hoursfrom the current time, require a turn-off of device 5600, requireInternet connection, and/or otherwise require user actions, etc. Inanother example, the device obtains only the event data from thecalendar application that meet priority criteria which are met, forexample, when the associated meetings are scheduled to start within 24hours from the current time, and/or require the user attendance, etc.Optionally, priority criteria are different for different applications.

Referring back to FIG. 56B, device 5600 detects an input correspondingto a request to scroll the user interface (e.g., timeline 5606) in aleft direction (e.g., detecting a leftward finger swipe gesture 5617).In response to detecting the leftward finger swipe gesture 5617, device5600 scrolls the user interface (e.g., timeline 5606) in a leftdirection, for example, to return to the display 5602 shown in FIG. 56A.

Optionally, as shown in the illustrated examples, an input correspondingto a request to scroll the user interface is a finger swipe gesture on atouch sensitive display of device 5600. A finger swipe gesture in afirst direction (e.g., left, right, up and down) corresponds to arequest to scroll the user interface in that first direction.

In some embodiments, horizontal scrolling allows a user to navigatethrough columns of different applications (e.g., swiping through columnsof applications while being fixed on one or more displayed times), whilevertical scrolling allows a user to navigate through rows of differenttimes (e.g., swiping through rows of times while being fixed ondisplayed one or more applications). Optionally, a concurrent verticaland horizontal scrolling (e.g., a two-dimensional scrolling, a diagonalscrolling) allows a user to navigate through columns and rows at thesame time.

For example, as shown in FIG. 56C, a user provides an inputcorresponding to a request to scroll the user interface (e.g., timeline5606) in a vertical direction by making an upward finger swipe gesture(e.g., 5619). In response to detecting the upward finger swipe gesture5619, device 5600 scrolls the user interface (e.g., timeline 5606) inthe direction of the finger swipe (the upward direction) to displayadditional rows of times representing later hours than the previouslydisplayed portion, as shown in FIG. 56D.

As shown in FIG. 56D, scrolling in response to the upward finger swipegesture 5619 causes the display of the portion shown in the previoususer interface screen 5602 in FIG. 56C to be replaced with display of adifferent portion shown in the new user interface screen 5602 d in FIG.56D. The new user interface screen 5602 d displays rows representing theadditional rows of time below the previously displayed portion,representing the later hours such as 4 pm, 5 pm, 6 pm, etc. Additionalaffordances (e.g., affordances for “Meeting 3,” “Meeting 4,” “Email 3,”and “Notification 3”) associated with the later hours are also displayedin the new portion shown in FIG. 56D.

In some embodiments, device 5600 detects an input corresponding to arequest to scroll the user interface in the opposite direction (e.g.,downward finger swipe gesture 5620), as shown in FIG. 56D. In responseto detecting the downward finger swipe gesture 5620, device 5600 scrollsthe user interface in the downward direction, for example, to return tothe screen 5602 shown in FIG. 56C. As will be apparent to persons ofordinary skill in the art, the amount by which the user interface (e.g.,timeline 5606) is scrolled can be determined based on various factors ofthe scroll input (e.g., the amount by which the finger is swiped, thevelocity of the finger swipe, the amount by which the rotatable inputmechanism is rotated, etc.), which are deemed within the scope of thepresent application.

In some embodiments, as shown in the illustrated examples, an inputcorresponding to a request to scroll the user interface is a fingerswipe gesture (e.g., a finger swipe in a first direction corresponds toa request to scroll the user interface in the first direction).Alternatively or additionally, an input corresponding to a request toscroll the user interface is rotation of rotatable input mechanism 5601provided on a side of device 5600.

In some embodiments, rotatable input mechanism 5601 can be pulled out tohave different positions (e.g., a first position if pulled out by afirst amount, a second position if pulled out by a second amount, etc.).If a user rotates rotatable input mechanism 5601 while rotatable inputmechanism 5601 is in a first position, the rotation causes the userinterface (e.g., timeline 5606) to scroll in a vertical direction (e.g.,upward rotation causes upward scrolling, and downward rotation causesdownward scrolling). If a user rotates input mechanism 5601 whilerotatable input mechanism 5601 is in a second position, the rotationcauses the user interface (e.g., timeline 5606) to scroll in ahorizontal direction (e.g., upward rotation causes rightward scrolling,and downward rotation causes leftward scrolling).

Further, in some embodiments, a user may provide an input correspondingto a request to zoom in or out the user interface (e.g., timeline 5606),as shown in FIGS. 56E-56G. For example, the user interface (e.g.,timeline 5606), which displays representations of event data arrangedrelative to each other based on their associated times and applications,includes a plurality of views (e.g., a first level view, a second levelview, a third level view, etc.). The plurality of views of the userinterface (e.g., timeline) can be navigated from one to another byzooming in or out the view of the user interface.

In some embodiments, the different views of the user interface (e.g.,timeline) have rows representing time blocks of a different interval.For example, a gap of two adjacent rows in a first level view of thetimeline (e.g., 5602 in FIG. 56E) represents an interval of an one-hourtime period; a gap of two adjacent rows in a second level viewrepresents an interval of a two-hour time period; a gap of two adjacentrows in a third level view (e.g., 5602 f in FIG. 56F) represents aninterval of a three-hour time period; a gap of two adjacent rows in afourth level view represents an interval of a four-hour time period; andso on. One or more views of the plurality of views of the user interface(e.g., timeline) may have a view that is different from a grid timeline,including, non-exclusively, a list view listing events in achronological order (e.g., 5602 i in FIG. 56I), or any other viewproperly formatted to notify the user of upcoming events aggregated fromtwo or more distinct application.

In some embodiments, as shown in FIG. 56E, a user provides an inputcorresponding to a request to zoom out the user interface (e.g.,timeline 5606) by making a multi-point finger gesture on atouch-sensitive display of device 5600 (e.g., a pinch-in gestureincluding two touch points 5621-a and 5621-b moving closer to each). Inresponse to detecting the input corresponding to a request to zoom outthe user interface (e.g., timeline 5606), device 5600 replaces the view5602 in FIG. 56E with display of a different view 5602 f of the userinterface shown in FIG. 56F. The zoomed-out view 5602 f in FIG. 56Fincludes rows representing a bigger time gap (e.g., a gap of twoadjacent rows in the view 5602 f represents a time gap of three hours,whereas a gap of two adjacent rows in the previous view 5602 in FIG. 56Erepresents a time gap of only one hour).

Optionally, in accordance with the zoomed-out view 5602 f in FIG. 56F,the size of the corresponding representations of the event data are alsoreduced, as shown in the reduced scale affordances 5622-a through5652-e, 5623-a through 5623-c, 5624-a, and partial affordance 5625-a inFIG. 56F. For example, in the first column associated with the calendarapplication, affordance 5622-a is a reduced scale representation of the“Meeting 1” associated with a one-hour time block from 9:00 am to 10:00am (e.g., in FIG. 56E); affordance 5622-b is a reduced scalerepresentation of the “Meeting 2” associated with a one-hour time blockfrom 12:00 pm to 1:00 pm (e.g., in FIG. 56E); affordance 5622-c is areduced scale representation of the “Meeting 3” associated with a30-minute time block from 2:30 pm to 3:00 pm (e.g., in FIG. 56E);affordance 5622-d is a reduced scale representation of the “Meeting 4”associated with a one-hour time block from 6:00 pm to 7:00 pm (e.g., inFIG. 56D); affordance 5622-e is a reduced scale representation of afirst meeting the next day associated with a one-hour time block from6:00 am to 7:00 am.

In the second column associated with the email application, affordance5623-a is a reduced scale representation of the “Email 1” associatedwith time 10:30 am (e.g., in FIG. 56E); affordance 5623-b is a reducedscale representation of the “Email 2” associated with time 1:00 pm(e.g., in FIG. 56E); affordance 5623-c is a reduced scale representationof the “Email 3” associated with time 6:00 pm (e.g., in FIG. 56D).Further, in the third column, affordances representing events from thenotification application from 3 am until 6 am of the next day areprovided in the user interface screen 5602 (e.g., affordance 5624-a is areduced scale representation of the “Notification 1” associated withtime 10:30 am in FIG. 56E). In the partially-displayed fourth column,the reduced scale representations for the events are similarly provided(e.g., affordance 5625-a is a reduced scale representation of the “Event1” from the “X” application shown in FIG. 56B).

In some embodiments, as shown in the illustrated example in FIG. 56F,the zoomed-out view may include representations of event data associatedwith more than a single day. The view 5602 f covers from 3 am to 6 am ofthe next day. Optionally, the change of day is visually indicated usinga day separator (e.g., 5626). By way of example, day separator 5626 is aline having different visual characteristics (e.g., thickness, color,shape such as solid or dotted, etc.) than other lines representing therows of times (e.g., dotted lines in FIG. 56F).

In some embodiments, as shown in the illustrated example in FIG. 56F, areduced scale representation (e.g., affordances 5622-a to 5622-e, 5623-ato 5623-c, 5624-a, and 56245-a in FIG. 56F) includes less textualinformation about the associated event data than a regular scalerepresentation (e.g., affordances 5609, 5610, 5611, and 5612 in FIG.56E), due to the reduced size. Optionally, reduced scale representationsinclude no textual information.

However, in some embodiments, the zoomed-out view 5602 f can allow auser to see more detailed information about a respective event byrequesting to display a callout view of the respective event. As shownin FIG. 56F, a user provides an input corresponding to a request todisplay a callout view of a selected event by making a finger tapgesture (e.g., 5627) on affordance 5622-d (which is a reduced scalerepresentation of the “Meeting 4” associated with a one-hour time blockfrom 6:00 pm to 7:00 pm as shown in FIG. 56D).

In response to detecting the input corresponding to a request to displaymore detailed information about the respective event 5622-d, device 5600displays a callout view (e.g., 5628), as shown in FIG. 56G, containingthe detailed information about the “Meeting 4” represented by thetouched affordance 5622-d. The detailed information about a calendarevent includes, for example, a meeting title, a meeting time, alocation, a subject, etc., as shown in callout view 5628 in FIG. 56G.Optionally, the callout view 5628 is displayed proximate to the touchedaffordance 5622-d and overlying at least a portion of the affordance5622-d.

In some embodiments, an input corresponding to a request to display moredetailed information about a respective event is a finger tap gesture,as shown in the illustrated examples. Optionally, an input correspondingto a request to display more detailed information about a respectiveevent is a push gesture on a depressible crown 5601 of device 5600. Forexample, a user may move a current focus (e.g., an affordance with acurrent focus is highlighted) among the displayed affordances, and asthe crown 5601 is depressed, the affordance with a current focus isselected.

Moreover, device 5600 allows a user to provide an input corresponding toa request to replace the user interface (e.g., timeline 5606) with anapplication view, as shown in FIGS. 56G and 56H. In FIG. 56G, a userprovides an input to end the timeline view and enter an application viewby making a tap and hold gesture (e.g., 5631) on affordance 5623-arepresenting the “Email 1” data from the email application. Optionally,the tap and hold gesture is a touch contact held for more than apredetermined time period (e.g., 2 seconds, 3 seconds, 4 seconds, etc.).

In response to detecting the input corresponding to a request to replacethe timeline user interface with an application user interface (e.g.,tap and hold gesture 5631 in FIG. 56G), device 5600 replaces the displayof the user interface screen 5602 f in FIG. 56G with display of an emailapplication user interface (e.g., 5637 in FIG. 56H) associated with theselected “Email 1” event data. The email application user interface 5637includes information related to the selected event data “Email 1,” suchas the subject field, from/to field, received time field, at least aportion of the body of message field, etc.

Optionally, an input corresponding to a request to replace the userinterface (e.g., timeline) with an associated application user interfaceis a sustained push gesture on a depressible button of crown 5601 formore than a predetermined time period.

Referring to back to FIG. 56G, in response to detecting an input (e.g.,pinch-in gesture 5630) corresponding to a request to further zoom outthe view 5602 f, device 5600 brings up a next level view (e.g., 5602 i)shown in FIG. 56I. This view 5602 i is not a grid timeline view, but alist view listing events in a chronological order. Optionally, the view5602 i displays a list of events for a first day (e.g., May 30, 2015)concurrently with a list of events for a second day (e.g., May 31,2015), as shown in FIG. 56I.

In some embodiments, as shown in the illustrated example in FIG. 56I,each listed event is displayed with its associated time(s) (e.g., 5633),brief summary (e.g., 5634), and/or affordance representing theassociated application (e.g., 5635). Optionally, each list is separatelyscrollable such that a user can scroll the top list without affectingthe bottom list in FIG. 56I.

Further, in the illustrated examples, device 5600 replaces the zoomedout view with a lower level view (e.g., zoomed-in view) in response todetecting an input corresponding to a request to zoom in the view (e.g.,pinch out gesture (not shown)).

FIGS. 57A-57F illustrate a flow diagram illustrating process 5700 forproviding context-specific user interfaces (e.g., user interfaceincluding timeline 5606 shown in FIGS. 56A-56I). In some embodiments,process 5700 may be performed at an electronic device with atouch-sensitive display, such as device 100 (FIG. 1A), 300 (FIG. 3), 500(FIG. 5) or 600 (FIGS. 6A and 6B). Some operations in process 5700 maybe combined, the order of some operations may be changed, and someoperations may be omitted. Process 5700 provides context-specific userinterfaces that give the user an immediate indication of various eventdata and associated times from at least two different applications,thus, providing a comprehensive and organized schedule of a day for theuser.

At block 5702, the device with a display, a memory and one or moreprocessors is turned on. At block 5704, the device obtains first eventdata from a first application (e.g., event data of “Meeting 1” from acalendar application in FIG. 56A). At block 5706, the device obtainssecond event data from a second application distinct from the firstapplication (e.g., event data of “Email 1” from an email application inFIG. 56A). At block 5708, the device determines a first time value(e.g., 9 am-10 am associated with the “Meeting 1”) associated with thefirst event data and a second time value (e.g., 10:30 am associated withthe “Email 1”) associated with the second event data, and a relativeorder of the first time value and the second time value.

At block 5710, the device displays, on the display, a user interface(e.g., user interface screen 5602 in FIG. 56A) including arepresentation of the first event data (e.g., affordance 5609) with arepresentation of the first time value (e.g., row 5606-b representing 9am-10 am with corresponding text 5607); and a representation of thesecond event data (e.g., affordance 5610) with a representation of thesecond time value (e.g., row 5606-b representing 10:30 am withcorresponding text 5607), wherein the representation of the first eventdata and the representation of the second event data are displayed withrespect to each other in accordance with the relative order of the firsttime value and the second time value and the respective values of thefirst time value and the second time value (e.g., affordances 5609, 5610and 5611 are displayed relative to each other based on their respectivetimes and relative order of the associated times as shown in userinterface screen 5602 in FIG. 56A).

At block 5712, the user interface further includes a representation ofthe first application in association with the representation of thefirst event data, and a representation of the second application inassociation with the representation of the second event data.

At block 5714, the device displays the representation of the first eventdata and the representation of the second event data with respect toeach other in accordance with the respective values of the first timevalue and the second time value includes displaying the representationof the first event data and the representation of the second event dataon a timeline (e.g., timeline 5606).

At block 5716, the timeline includes a plurality of rows and columns(e.g., rows 5606-a and columns 5606-b). The representation of the firstevent data is displayed at a first column and a first row of thetimeline, the first column comprising the representation of the firstapplication (e.g., column 5606-a with affordance 5603 representing thecalendar application), and the first row comprising the representationof the first time value (e.g., row 5606-b representing 9 am-10 am withcorresponding text 5607). The representation of the second event data isdisplayed at a second column and a second row of the timeline, thesecond column comprising the representation of the second application(e.g., column 5606-a with affordance 5604 representing the emailapplication), and the second row comprising the representation of thesecond time value (e.g., row 5606-b representing 10:30 am withcorresponding text 5607).

At block 5718, the device detects an input corresponding to a request toscroll the user interface (e.g., timeline) in a first direction. Atblock 5720, the display of the electronic device is touch sensitive, anddetecting the input corresponding to a request to scroll in the firstdirection comprises detecting a first gesture on the touch sensitivedisplay (e.g., horizontal finger swipe gesture 5613 or 5615). At block5722, the electronic device further comprises a rotatable inputmechanism (e.g., 5601), and detecting the input corresponding to arequest to scroll in the first direction comprises detecting rotation ofthe rotatable input mechanism while the rotatable input mechanism is ina first configuration.

At block 5724, in response to detecting the input corresponding to arequest to scroll the user interface (e.g., timeline) in a firstdirection, the device scrolls the user interface (e.g., timeline) in thefirst direction in accordance with the input to display at least arepresentation of a third time value different from the first time valueand the second time value. At block 5726, scrolling the user interfacein the first direction in accordance with the input to display at leasta representation of a third time value different from the first timevalue and the second time value comprises replacing display of a portionof the user interface (e.g., a portion shown in user interface screen5602 in FIG. 56A) with display of a different portion of the userinterface (e.g., a different portion shown in user interface screen 5602b in FIG. 56B).

At block 5728, in response to detecting the input corresponding to arequest to scroll the timeline in a first direction, the device scrollsthe timeline (e.g., 5606) in the first direction in accordance with theinput to display at least one row different from the first row and thesecond row. At block 5730, scrolling the timeline in the first directionin accordance with the input to display at least one row different fromthe first row and the second row comprises replacing display of aportion of the timeline (e.g., a portion shown in user interface screen5602 in FIG. 56A) with display of a different portion of the timeline(e.g., a different portion shown in user interface screen 5602 b in FIG.56B).

At block 5732, the device detects a second input corresponding to arequest to scroll the user interface (e.g., timeline) in a seconddirection. At block 5734, the display of the electronic device is touchsensitive, and detecting the input corresponding to a request to scrollin the second direction comprises detecting a second gesture on thetouch sensitive display (e.g., vertical finger swipe gestures 5619 or5620). At block 5736, the electronic device further comprises arotatable input mechanism (e.g., 5601), and detecting the inputcorresponding to a request to scroll in the second direction comprisesdetecting rotation of the rotatable input mechanism while the rotatableinput mechanism is in a second configuration.

At block 5738, in response to detecting the second input correspondingto a request to scroll the user interface (e.g., timeline) in a seconddirection, the device scrolls the user interface (e.g., timeline) in thesecond direction in accordance with the second input to display at leasta representation of a third application different from the firstapplication and the second application. At block 5740, scrolling theuser interface in the second direction in accordance with the secondinput to display at least a representation of a third applicationdifferent from the first application and the second applicationcomprises replacing display of a portion of the user interface (e.g., aportion shown in user interface screen 5602 in FIG. 56C) with display ofa different portion of the user interface (e.g., a portion shown in userinterface screen 5602 d in FIG. 56D).

At block 5742, in response to detecting the second input correspondingto a request to scroll the timeline (e.g., 5606) in a second direction,the device scrolls the timeline in the second direction in accordancewith the second input to display at least one column different from thefirst column and the second column. At block 5744, scrolling thetimeline in the second direction in accordance with the second input todisplay at least one column different from the first column and thesecond column comprises replacing display of a portion of the timeline(e.g., a portion shown in user interface screen 5602 in FIG. 56C) withdisplay of a different portion of the timeline (e.g., a portion shown inuser interface screen 5602 d in FIG. 56D).

At block 5746, the user interface comprises a plurality of views, andwhile displaying a first level view out of the plurality of views of theuser interface, the first level view with representations of times in aninterval of a first time period, the device detects a third inputcorresponding to a request to display a second level view distinct fromthe first level view out of the plurality of views of the user interface(e.g., pinch-in or out gestures). At block 5748, the display of theelectronic device is touch sensitive; and detecting the third inputcorresponding to a request to display a second level view distinct fromthe first level view out of the plurality of views of the user interfacecomprises detecting two or more simultaneous touches on thetouch-sensitive display that are continuously moved to vary the distancebetween the two or more touches (e.g., touch points 5621-a and 5621-bfor a pinch-in gesture in FIG. 56E).

At block 5750, in response to detecting the third input corresponding toa request to display a second level view distinct from the first levelview out of the plurality of views of the user interface (e.g., pinch-inor out gestures), the device replaces the display of the first levelview (e.g., a view shown in user interface screen 5602 in FIG. 56E, withan interval of a one-hour timer period) with display of the second levelview, wherein the second level view includes representations of times inan interval of a second time period that is distinct from the first timeperiod (e.g., a zoomed-out view shown in user interface screen 5602 f inFIG. 56F, with an interval of a three-hour time period, or a list-viewshown in user interface screen 5602 i in FIG. 56I).

At block 5752, while displaying the user interface with therepresentation of the first event data in association with therepresentation of the first time value and the representation of thesecond event data in association with the representation of the secondtime value, the device detects a fourth input corresponding to a requestto select the representation of the first event data (e.g., a tapgesture). At block 5754, the display of the electronic device is touchsensitive; and detecting the fourth input corresponding to a request toselect the representation of the first event data comprises detecting atap gesture on the representation of the first event data displayed onthe touch sensitive display (e.g., tap gesture 5627 in FIG. 56F).

At block 5756, in response to detecting the fourth input correspondingto a request to select the representation of the first event data (e.g.,a tap gesture), the device displays a callout view (e.g., 5628 in FIG.56G) proximate to the representation of the first event data, thecallout view including additional information about the first event databeyond the associated first time value and the first application,wherein the display of the callout view overlays at least a portion ofthe representation of the first event data.

At block 5757, while displaying the user interface with therepresentation of the first event data in association with therepresentation of the first time value and the representation of thesecond event data in association with the representation of the secondtime value, the device detects a fifth input on the representation ofthe first event data (e.g., tap and hold gesture 5631 in FIG. 56G).

At block 5760, in response to detecting the fifth input on therepresentation of the first event data (e.g., a tap and hold gesture),the device ceases to display the user interface, and displays a userinterface of the first application in relation to the first event data(e.g., email application user interface 5602 i in FIG. 56H).

Note that details of the processes described above with respect tomethod 5700 (e.g., FIG. 57) are also applicable in an analogous mannerto the methods and techniques described elsewhere in this application.For example, other methods described in this application may include oneor more of the characteristics of method 5700. For example, the devices,hardware elements, inputs, interfaces, modes of operation, faces, timeindicators, and complications described above with respect to method5700 may share one or more of the characteristics of the devices,hardware elements, inputs, interfaces, modes of operation, faces, timeindicators, and complications described elsewhere in this applicationwith respect to other methods. Moreover, the techniques described abovewith respect to method 5700 may be used in combination with any of theinterfaces, faces, or complications described elsewhere in thisapplication. For brevity, these details are not repeated elsewhere inthis application.

The operations in the information processing methods described above maybe implemented by running one or more functional modules in informationprocessing apparatus such as general purpose processors or applicationspecific chips. These modules, combinations of these modules, and/ortheir combination with general hardware (e.g., as described above withrespect to FIGS. 1A, 1B, 3, 5A, and 5B) are all included within thescope of the techniques described herein.

In accordance with some embodiments, FIG. 58 shows an exemplaryfunctional block diagram of an electronic device 5800 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 5800 are configured to perform the techniques described above(e.g., including process 5700). The functional blocks of the device 5800are, optionally, implemented by hardware, software, or a combination ofhardware and software to carry out the principles of the variousdescribed examples. It is understood by persons of skill in the art thatthe functional blocks described in FIG. 58 are, optionally, combined orseparated into sub-blocks to implement the principles of the variousdescribed examples. Therefore, the description herein optionallysupports any possible combination or separation or further definition ofthe functional blocks described herein

FIG. 58 shows exemplary functional blocks of an electronic device 5800that, in some embodiments, performs the features described above. Asshown in FIG. 58, an electronic device 5800 includes a display unit 5802configured to display graphical objects and a processing unit 5810coupled to display unit 5802. In some embodiments, device 5800 furtherincludes a touch-sensitive surface unit 5804 configured to receive usergestures, a rotatable input mechanism 5806, and or one or more RF units5808 configured to detect and communicate with external electronicdevices. In some embodiments, processing unit 5810 includes a detectingunit 5812 configured to detect various inputs provided by a user (e.g.,touch inputs, mechanism inputs), and an obtaining unit 5814 configuredto obtain event data from various applications (e.g., obtain meetingevent data from a calendar application and email data from an emailapplication, etc.).

In some embodiments, processing unit 5810 includes a display enablingunit 5816, a determining unit 5818, a scroll enabling unit 5820, a zoomenabling unit 5822, a callout view enabling unit 5824, and/or anapplication view enabling unit 5826. For example, the display enablingunit 5816 is configured to cause a display of a user interface (orportions of a user interface) in conjunction with the display unit 5802.For example, the display enabling unit 5816 may be used for displaying aportion of a user interface (e.g., timeline 5606) and updating adisplayed portion in accordance with various inputs from a user. Thedetermining unit 5818 may be used for determining respective timesassociated with the obtained event data from various applications usingthe obtaining unit 5814, as well as relative order of the timesassociated with such event data.

The scroll enabling unit 5820 may be used for scrolling the userinterface (e.g., timeline 5606) in accordance with various scroll inputsfrom a user (e.g., horizontal finger swipe gesture 5613 and 5617 forhorizontal scroll inputs, and vertical finger swipe gestures 5619 and5620) for vertical scroll inputs). The scroll enabling unit 5820 enablesthe user to scroll through columns of applications in the timeline(e.g., 5606) based on the horizontal scroll inputs. The scroll enablingunit 5820 enables the user to scroll through rows of times in thetimeline (e.g., 5606) based on the vertical scroll inputs. The zoomenabling unit 5822 may be used for zooming in or out the user interface(e.g., timeline 5606) in accordance with various inputs to zoom in orout the user interface (e.g., pinch-in gesture with two touch points5621-a and 5621-b in FIG. 56E). The zoom enabling unit 5822 enablesreplacing a first level view of the timeline with a second level view ofthe timeline, wherein the first level view arranges the times in aninterval of a first time period, and the second level view arranges thetimes in an interval of a second time period different from the firsttime period.

The callout view enabling unit 5824 may be used for displaying a calloutview based on an input corresponding to a request to displayed a moredetailed view of a selected event (e.g., tap gesture 5627 in FIG. 56F).The callout view enabling unit 5824 enables display of the callout viewoverlying at least a portion of the event affordance touched by the user(e.g., callout view 5628 overlying at least a portion of the affordance5622-d in FIGS. 56F and 56G). The application view enabling unit 5826may be used for replacing the display of the user interface (e.g.,timeline) with display of an application user interface upon an inputcorresponding to a request to display the application view associatedwith the selected event (e.g., tap and hold gesture 5631 in FIG. 56G).The application view enabling unit 5826, upon detecting the input 5631,ceases the display of the timeline 5606 and starts displaying the emailapplication view containing the selected email data (e.g., 5602 i inFIG. 56I). The units of FIG. 58 may be used to implement the varioustechniques and methods described above with respect to FIGS. 56A-56I and57A-57F.

For example, the processing unit 5810 is configured to obtain firstevent data from a first application (e.g., with obtaining unit 5812) andobtain second event data from a second application distinct from thefirst application (e.g., with obtaining unit 5812). The processing unit5810 is configured to determine (e.g., with determining unit 5818) afirst time value associated with the first event data and a second timevalue associated with the second event data and a relative order of thefirst time value and the second time value. The processing unit 5810 isconfigured to display (e.g., with display enabling unit 5816), on thedisplay (e.g., display unit 5802), a user interface including: arepresentation of the first event data with a representation of thefirst time value; and a representation of the second event data with arepresentation of the second time value. The representation of the firstevent data and the representation of the second event data are displayedwith respect to each other in accordance with the relative order of thefirst time value and the second time value and the respective values ofthe first time value and the second time value.

The processing unit 5810 is configured to detect (e.g., with detectingunit 5812) an input corresponding to a request to scroll the userinterface in a first direction. In response to detecting the inputcorresponding to a request to scroll the user interface in a firstdirection, the processing unit 5810 is configured to scroll (e.g., withscroll enabling unit 5820) the user interface in the first direction inaccordance with the input to display at least a representation of athird time value different from the first time value and the second timevalue. The scroll enabling unit 5820, for example, enables scrollingsuch that scrolling the user interface in the first direction inaccordance with the input to display at least a representation of athird time value different from the first time value and the second timevalue comprises replacing display of a portion of the user interfacewith display of a different portion of the user interface.

The processing unit 5810 is configured to detect (e.g., with detectingunit 5812) a second input corresponding to a request to scroll the userinterface in a second direction. In response to detecting the secondinput corresponding to a request to scroll the user interface in asecond direction, the processing unit 5810 is configured to scroll(e.g., with scroll unit 5820) the user interface in the second directionin accordance with the second input to display at least a representationof a third application different from the first application and thesecond application. The scroll enabling unit 5820 enables scrolling suchthat scrolling the user interface in the second direction in accordancewith the second input to display at least a representation of a thirdapplication different from the first application and the secondapplication comprises replacing display of a portion of the userinterface with display of a different portion of the user interface.

In some embodiments, the user interface comprises a plurality of views,and while displaying a first level view out of the plurality of views ofthe user interface, the first level view with representations of timesin an interval of a first time period, the processing unit 5810 isconfigured to detect (e.g., with detecting unit 5812) a third inputcorresponding to a request to display a second level view distinct fromthe first level view out of the plurality of views of the userinterface. In response to detecting a third input corresponding to arequest to display a second level view distinct from the first levelview out of the plurality of views of the user interface, the processingunit 5810 is configured to replace the display of the first level viewwith display of the second level view (e.g., with zoom enabling unit5822), wherein the second level view includes representations of timesin an interval of a second time period that is distinct from the firsttime period.

In some embodiments, while displaying the user interface with therepresentation of the first event data in association with therepresentation of the first time value and the representation of thesecond event data in association with the representation of the secondtime value, the processing unit 5810 is configured to detect (e.g., withdetecting unit 5812) a fourth input corresponding to a request to selectthe representation of the first event data. In response to detecting thefourth input corresponding to a request to select the representation ofthe first event data, the processing unit 5810 is configured to displaya callout view proximate to the representation of the first event data(e.g., with callout view enabling unit 5824), the callout view includingadditional information about the first event data beyond the associatedfirst time value and the first application, wherein the display of thecallout view overlays at least a portion of the representation of thefirst event data.

In some embodiments, while displaying the user interface with therepresentation of the first event data in association with therepresentation of the first time value and the representation of thesecond event data in association with the representation of the secondtime value, the processing unit 5810 is configured to detect (e.g., withdetecting unit 5812) a fifth input on the representation of the firstevent data. In response to detecting the fifth input on therepresentation of the first event data, the processing unit 5810 isconfigured to cease to display the user interface and display a userinterface of the first application in relation to the first event data(e.g., with application view enabling unit 5826).

The functional blocks of the device 5800 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 58 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

The operations described above with reference to FIGS. 57A-57F are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.58. For example, obtaining operations 5704 and 5706, determiningoperation 5708, displaying operation 5710, detecting operations 5718,5732, 5746, 5752 and 5758, scrolling operations 5724 and 5738, zoomoperation 5750, callout view display operation 5756, and applicationview display operation 5760 may be implemented by event sorter 170,event recognizer 180, and event handler 190. Event monitor 171 in eventsorter 170 detects a contact on touch-sensitive display 112, and eventdispatcher module 174 delivers the event information to application136-1. A respective event recognizer 180 of application 136-1 comparesthe event information to respective event definitions 186, anddetermines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub event,such as activation of an affordance on a user interface. When arespective predefined event or sub-event is detected, event recognizer180 activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 may utilize or call data updater176 or object updater 177 to update the application internal state 192.In some embodiments, event handler 190 accesses a respective GUI updater178 to update what is displayed by the application. Similarly, it wouldbe clear to a person having ordinary skill in the art how otherprocesses can be implemented based on the components depicted in FIGS.1A-1B.

FIGS. 59A-59F depict exemplary user interface screens for a typographicmodular face interface and a corresponding interface for editingsettings of the typographic modular face. A typographic modularinterface may be a display interface that displays information arrangedinto modules or platters or slots, wherein the information is displayedin typographic form, without any use (or with limited use) ofnon-standard symbols, logos, and glyphs. The information displayed maycorrespond to or be related to the present time, such that theinformation is regularly updated to reflect the most recent information.The edit interface may provide an interface for selecting color settingsfor the interface, for selecting which complications (if any) are to bedisplayed in which platters, and for selecting the amount of informationthat is displayed as a part of one or more of the complications. In alower-density, higher-privacy setting, less information may be displayedin each complication, and the information may be displayed in a largerfont size; in a higher-density, lower-privacy setting, additionalinformation may be displayed in each complication, and some or all ofthe information may be displayed in a smaller font size. Changes tocolor settings, complication platter assignments, and density/privacysettings may be made by rotating a rotatable input mechanism while in anedit interface, and the edit interface may be accessed from thetypographic modular interface by executing a hard press (e.g., executinga touch contact having a characteristic intensity above an intensitythreshold).

FIG. 59A shows exemplary user interface screen 5950 that device 5900 candisplay on display 5902. In some embodiments, device 5900 may be one ormore of devices 100 (FIG. 1), 300 (FIG. 3), and/or 500 (FIG. 5). Theelectronic device has touch-sensitive display 5902 (e.g., touchscreen504).

Users rely on personal electronic devices to keep time throughout theday and to quickly reference time-dependent information, such asinformation about messages, appointments, the weather, news, and otherdata. It is becoming increasingly desirable to present the user withinteractive user interfaces that promote user interaction with apersonal electronic device. Indicating the time alongside a typographicrepresentation of time-dependent information may enhance a user'sinteraction with the device. Furthermore, allowing a user to set aprivacy or density setting that controls the level of detail with whichinformation is displayed on a device may enhance privacy and encourage auser to more freely and comfortably interact with the device. Increasingthe level of simplicity, versatility, customizability, and privacy ofthe interface screen may enhance and prolong user interactions with thedevice.

Accordingly, provided herein are context-specific user interfaces thatinclude a time-indicator as well as a plurality of slots (e.g.,platters, modules) for displaying time-dependent information such ascomplications or notifications. A user may wish for such an interface tobe customizable such that the content, location, privacy level, andappearance of each of the complications can be modified by the user. Auser may wish for all information to be displayed in typographic form,without the use (or with minimal use) of non-standard symbols, logos, orglyphs, so that the user does not have to learn the meaning of customsymbols. A user may wish for a privacy or density setting of aninterface to be modifiable so that it may be used in different settingswhen the user desires additional information to be presented or lessinformation to be presented.

Device 5900 may display interface screen 5950 on display 5902. Interfacescreen 5950 may be referred to as a typographic modular face, because itmay display typographic information (as opposed to symbols, logos,graphics, or glyphs) on a customizable modular face (e.g., an interfacehaving a plurality of modules, platters, or slots). Interface screen5950 comprises clock 5908, which may indicate the current time (or, insome embodiments, a non-current time). Interface screen 5950 furthercomprises complications 5910 a, 5912 a, 5914 a, and 5916 a, which aredisplayed in a first platter, a second platter, a third platter, and afourth platter, respectively. Each of the platters may correspond to apredefined location on interface screen 5950 on display 5902, with eachplatter being configured to display information about a respectivesubject matter.

In the embodiment shown in FIG. 59A, complication 5910 a is a datecomplication that indicates a day of the week and the date of the month(Friday the 23rd). Complication 5912 a is a calendar complication thatindicates the time of day of the next appointment or event in a calendar(11:30 a.m.). Complication 5914 a is a weather complication thatindicates a temperature of the weather (72°). Complication 5916 a is aworld clock complication that indicates a time in another time zone(6:09 p.m.).

In the embodiment shown, the complications 5910 a-5916 a are displayedin a first density state that displays less information than a seconddensity state. The first density state may correspond to a first privacystate, which may be used to enhance privacy such that onlookers can seeonly a minimal amount of information on the display of the device, whilethe user himself may be aware of the context that gives meaning to theminimal information displayed in the first density state. For example,an onlooker might not know what “11:30” means in complication 5912 b,but the user may know, simply from being reminded of the time, that11:30 is the time of an upcoming meeting.

FIG. 59A further depicts user input 5918, which is a hard-press userinput (a touch contact whose characteristic intensity is above anintensity threshold) detected at the depicted location. In otherembodiments, any other suitable user input may be used. In response todetecting user input 5918, device 5900 may display an edit interface forediting the typographic modular interface (e.g., for editing interfacescreen 5940 or 5950).

FIG. 59B depicts edit interface screen 5960 for editing display settingsfor a typographic modular interface such as the interfaces depicted byinterface screens 5950 and 5960. An edit interface screen may includesome or all of the elements of a typographic modular face screen, and insome embodiments may be considered or referred to as a typographicmodular face screen. In some embodiments, an edit interface screen mayinclude one or more visual indications that indicate that the interfaceis an edit interface screen and/or that indicate that the device is inan editing state.

Edit interface screen 5960, for example, is identical to interfacescreen 5950 except for paging affordances 5919 displayed at the top ofedit interface screen 5960. Paging affordances 5919 indicate that editinterface screen 5960 is an edit interface screen. That is, dots 5919may signal to the user that the device is in a state configured to editthe device face, rather than in a state configured merely to display theface itself. Paging affordances 5919 further indicate that the editinterface comprises two pages or screens (as indicated by the number ofpaging affordances), and that interface screen 5960 is the leftmost oftwo screens (as indicated by the leftmost dot being solid/filled and therightmost dot being hollow). In the example shown, leftmost editinterface screen 5960 is a screen for modifying color settings of thetypographic modular interface. The manner in which color settings may bemodified is discussed in further detail below.

FIG. 59B further depicts user input 5920, which is a rotation ofrotatable input mechanism 5904. In other embodiments, any other suitableuser input may be used. In response detecting user input 5920, device5900 may edit a density/privacy setting of the typographic modular face,and may display the result of the edited setting.

FIG. 59C depicts the result of the detection of user input 5920. Inresponse to detecting user input 5920, the device displays interfacescreen 5970, which is an updated version of interface screen 5960;interface screen 5970 is still the leftmost of two pages in the editinterface for the typographic modular face, but now reflects the changemade to the density setting in response to the detection of user input5920.

In response to detecting the rotation of the rotatable input mechanism5904, device 5900 has changed the privacy/density setting from a firstdensity state to a second density state, and the complications 5910-5916are displayed in a second density state corresponding to additionalinformation and a reduction in privacy.

In some embodiments, a device may be capable of displayingcomplications, other user interface objects, or other information inmultiple density settings. In some embodiments, a second density settingmay correspond to displaying additional information in the same platteras compared to the first density setting, making the presentation ofinformation by complications in the second density setting denser. Insome embodiments, the second density state may correspond to a secondprivacy state, and may be used to display more information when a userwould rather have access to more information than hide the informationfor the sake of privacy. The additional information may correspond tothe same subject matter as the information that is displayed in thefirst density state; in some embodiments, it may represent a differentportion (or additional portions) of the same underlying data from whichthe first information was derived. The additional information may bepredetermined to be more sensitive than the information that isdisplayed in the first density state. Because the additional informationdisplayed in the second density state may be more sensitive informationcorresponding to more sensitive data, the additional information may bedisplayed at a smaller font size than the first information, to enhancesecurity by making it more difficult for onlookers to read the text ofthe additional information.

In the example shown, in the second density setting, date complication5910 b additionally displays a month and year (April 2015). Calendarcomplication 5912 b additionally displays a name of the next appointment(“Design Meeting”). Weather complication 5914 b additionally displaysthe location for which the weather is being displayed (Cupertino,Calif.) and additional information about the weather (“Partly Cloudy”).World clock complication 5916 b additionally displays the city for whichthe world clock time is displayed (London, England) and a differencebetween the time in that city and the time displayed on clock 5908 (“+8hours”).

In some embodiments, a user may rotate a rotatable input mechanism whilein the edit state (regardless of page) in either direction in order tocycle through or scroll through two or more density/privacystates/settings. In some embodiments, the density/privacy settings ofall displayed complications are updated together, while in otherembodiments the density/privacy setting of each complication may beindividually modifiable. In some embodiments, there may more than twodensity states.

For example, in some embodiments there may be three density/privacystates/settings, such that a further rotation of rotatable inputmechanism 5904 in the direction of input 5920 may cause additionalsupplemental information to be displayed in one or more of the platters.The additional supplemental information displayed in the thirddensity/privacy state may correspond, for each platter, to the sameunderlying subject matter or information source as the informationdisplayed in the first two density states. In some embodiments, theinformation corresponding to the third density state may bepredetermined to be of a higher sensitivity than the informationdisplayed in the first two states, thereby corresponding to an evenhigher privacy setting. In some embodiments, the additional supplementalinformation displayed in the third density state may be displayed in aneven smaller font size than the information corresponding to the seconddensity state, thereby being even more difficult for onlookers to read.

FIG. 59C further depicts user input 5922, which is a tap input detectedon display 5902 at a location corresponding to complication 5912 b inthe second of four complication platters. In other embodiments, anyother suitable user input may be used. In response detecting user input5922, device 5900 may select a complication and/or a platter forediting, and may display the selected complication/platter in ahighlighted manner.

In FIG. 59D, complication 5912 b is selected for editing in editinterface screen 5980, which is an updated version of edit interfacescreen 5970. Edit interface screen 5980 is an interface screen forediting a color setting associated with one or more of the displayedcomplications. In the example shown, complication 5912 b is displayed ashighlighted by being displayed in a larger size than the othercomplications, and by having the text of the complication bolded. Inother embodiments, the selected complication may be displayed with a boxor outline around it, in a different position, in a different size, in ahighlight text color, with a background color, in italics, underlined,in a different font, or in any other manner suitable to visuallydistinguish it.

FIG. 59D further depicts user input 5924, which is a rotation ofrotatable input mechanism 5904. In other embodiments, any other suitableuser input may be used. In response to detecting user input 5924, device5900 may modify a color setting of a selected complication/platter.

For example, there may be a predefined selection of color settings eachcorresponding to a color, series of colors, pattern of colors, oranimation by which a color setting changes in time. In some embodiments,one or more of the color settings is a gradient color setting or apattern color setting that renders the complication text (in the firstor second density state) as a continuous color gradient or patternacross the different letters and numbers in the complication. Thepredefined color settings may be arranged into an ordered progression.When the user selects a complication for editing and rotates therotatable input mechanism, the setting may be modified by cycling orscrolling through the ordered progression to a next or previous colorsetting in accordance with a direction of the rotation of the input. Insome embodiments, the ordered progression may loop around from the lastsetting to the first.

In some embodiments, a user may edit a color setting of more than one ofthe complications/platters, or of all of the complications/platters, atthe same time. For example, color themes may be predetermined and savedon the device (or available to the device by network communication),such that a user may select a single theme that assigns a color settingto more than one or all of the complications/platters. In someembodiments, themes may assign a predetermined color setting to apredetermined platter. In some embodiments, themes may assign apredetermined color setting to a predetermined type of complication,regardless of the platter in which it appears. In some embodiments, atheme may be a gradient theme or a pattern theme that renders more thanone of the complications/platters, or all of the complications/platters,as a continuous gradient or a continuous pattern across the letters andnumbers in the multiple complications/platters.

In the example shown in FIG. 59C, the modification to a color settingaffects only the selected complication, selected complication 5912 b,although the modification itself is not shown by the black-and-whitefigure.

FIG. 59D further depicts user input 5926, which is a leftward swipegesture applied to the touch-sensitive screen 5902. In otherembodiments, any other suitable user input may be used. In response todetecting user input 5926, device 5900 may display a page of the editinterface that is located to the right of the current page.

FIG. 59E depicts edit interface screen 5990, which is displayed as aresult of the detection of user input 5926 in FIG. 59D. In response todetecting user input 5926, the device displays edit interface screen5990. Edit interface screen 5990 is the rightmost of two edit interfacescreens in the depicted edit interface, as indicated by pagingaffordances 5919 displayed at the top of edit interface screen 5990.Paging affordances 5919 have been updated such that the left dot ishollow and the right dot is solid/filled, showing that the right of twopages is the currently displayed page. In some embodiments, an animationmay display a transition from the one page to another, while in someembodiments, the page may remain substantially unchanged and the pagingaffordances may be the only displayed element that changes when the userpages left or right. In the displayed example, edit interface screen5990 is otherwise identical to edit interface 5980, depicting clock 5908and complications 5910 b-5916 b. In the depicted example, complication5912 b is selected for editing and is highlighted by being displayed ata larger size than the other complications. In the example depicted, theselection of complication 5912 b for editing has been maintained fromthe previous edit interface screen 5980; however, in some otherembodiments, paging between edit interface screens may cause acomplication that is selected for editing to be deselected.

FIG. 59E further depicts user input 5928, which is a rotation ofrotatable input mechanism 5904. In other embodiments, any other suitableuser input may be used. In response to detecting user input 5928, device5900 may modify the type of complication that is displayed in theplatter in which the selected complication is currently displayed. Thatis, the device may replace the selected complication with another typeof complication.

For example, there may be a predefined selection of complications thatare available to be displayed in one or more of the platters. In someembodiments, the one or more complications are arranged into an orderedprogression. When the user selects a complication for editing androtates the rotatable input mechanism, the complication may be replacedby a next or previous complication in the ordered progression ofcomplications by cycling or scrolling through the ordered progression toa next or previous complication in accordance with a direction of therotation of the input. In some embodiments, the ordered progression mayloop around from the last complication to the first.

In some embodiments, a complication that is selected to be displayed ina platter may retain the color setting of the complication that waspreviously displayed in the platter. In some embodiments, such as thosein which certain colors are associated with certain types ofcomplications, a newly selected complication may be displayed in adifferent color than the complication that was previously displayed inthe platter.

The complications available to be displayed may include one or morecomplications relating to one or more of the following: date, calendar,weather, world clock, sunrise/sunset, time, stocks, alarm, stopwatch,activity, exercise, standing, the moon, music, Nike, Tesla charge,charge of device (e.g., device 5900), other device charge, city manager,MLB, other sports, Twitter, other social media, and messages. Theforegoing list of complications is merely exemplary, not exhaustive. Insome embodiments, an option available for one or more of the plattersmay further be to display no complications in the platter. The “blank”option may be included as an option in the ordered progression ofcomplications and may be accessible in the edit interface in the samemanner as complications are accessible.

In some embodiments, a user may select a complication for a givenplatter on a slot-by-slot basis, by tapping platters/complications toselect the platter, and then using the rotatable input mechanism tocycle through available complications and assign them to the platter. Insome embodiments, a user may assign a complication to more than oneplatter at a time, or to all of the platters at one time, for example byselecting a predetermined or curated “complication set.” The device mayhave complication sets saved on the device, or they may be accessible bythe device via a network connection, and the user may select a set thatassigns more than one complication to more than one respective platter.For example, a user may select a “stocks” complication set, and thedevice may assign complications pertaining to the NASDAQ, the Dow Jones,and the S&P 500 to respective platters.

FIG. 59F displays edit interface screen 5992, which is an updatedversion of edit interface screen 5990 reflecting the response by device5900 to the detection of user input 5928 in FIG. 59E. In response todetecting user input 5928, which is a rotation of rotatable inputmechanism 5902, device 5900 updates the complication that is assigned tothe second platter by assigning a next complication in the orderedprogression of complications to the slot. In the depicted example, thecomplication that follows previously displayed calendar complication5912 b in the ordered progression is S&P 500 complication 5930 b, whichdisplays information about the performance of the Standard & Poor'sstock market index (e.g., a gain of 54.48 points). Note that S&P 500complication 5930 b is displayed in a second density/privacy state, asare the other complications in FIG. 59F. In some embodiments, if thedensity/privacy state were changed to the first state, then thecomplication would display less information, such as by suppressingdisplay of the name of the stock index. In some embodiments, if thedensity/privacy state were changed to an even higher density setting,then the complication would display additional information, such ashighly sensitive information pertaining to a user's personal portfolioperformance.

In some embodiments, users may be able to modify settings pertaining toother aspects of the typographic modular face, including but not limitedto: the number of modules/slots, the position of the modules, thealignment and justification of text within the modules, the font of thetext, and the size of the font. In some embodiments, these and othersetting may be modified in similar manners as described above byaccessing additional edit interface screens that may be represented byadditional paging affordances.

FIGS. 60A-60F are flow diagrams illustrating a method for providing andsupplementing information in accordance with user inputs in accordancewith some embodiments. Method 6000 is performed at a device (e.g., 100,300, 500, 5900) with a display, a rotatable input mechanism, and one ormore processors. Some operations in method 6000 may be combined, theorder of some operations may be changed, and some operations may beomitted.

As described below, method 6000 provides an intuitive way to providingand supplementing information. The method reduces the cognitive burdenon a user for accessing information pertaining to various densitysettings, various privacy levels, and various subject matters, therebycreating a more efficient human machine interface. For battery-operatedcomputing devices, enabling a user to more quickly and more efficientlyaccess, configure, and navigate a user interface for providing andsupplementing information, including information corresponding tovarious privacy levels, conserves power and increases the time betweenbattery charges.

In FIG. 60A, at block 6002, method 6000 is performed at an electronicdevice having a display, a battery, and one or more processors. Anexemplary device is device 5900 of FIGS. 59A-6F, which has display 5902and a rotatable input mechanism 5904.

A block 6004, the device receives data relating to a first subjectmatter. In some embodiments, the received data may be any data that isstored on the device or accessed by the device through networkcommunications, including data received through applications or programsrun by the device. In some embodiments, the received data may be datacorresponding to a first application and/or first subject matter thatmay be presented, by the device, in a complication or other userinterface object.

At block 6006, the device displays information relating to a firstportion of the received data. In some embodiments, the data is logicallydivided into multiple portions, segments, sections, or the like, uponbeing received or initially accessed by the device. In some embodiments,the device may divide the received data into multiple portions,segments, sections, or the like in accordance with predefined rules ordynamic analysis. In some embodiments, the received data may be dividedor assigned into multiple portions, segments, sections, or the like inaccordance with user inputs or instructions.

In some embodiments, information relating to a first portion of thereceived data may be displayed in any visual format that is suitable tobe viewed by a user, including in textual, numerical, image-based,animation-based, and/or video-based format.

In the depicted example of FIG. 59A, device 5900 receives, among otherinformation, information from a calendar application. The subject matterof the information received from the calendar application is calendardata, events, and the like. In the depicted example, a first portion ofthe calendar data comprises information about a time of an upcomingcalendar event, the time of which is 11:30. In the depicted example,complication 5912 a displays the text “11:30” in accordance with thefirst portion of the received data.

At block 6008, optionally, displaying the first information comprisesdisplaying the first information in a first predetermined portion of auser interface. In some embodiments, a user interface may have one ormore predefined portions in which information may be displayed. In someembodiments, the portions may be predefined by the device, while in someembodiments the portions may be defined in accordance with user input.In some embodiments, a user interface may have multiple slots, platters,or modules that may each be configured to display information relatingto a respective subject matter. In the displayed example of FIG. 59A,interface screen 5950 includes four platters displaying, respectively,complications 5910 a-5910 d, each of which correspond to a distinctsubject matter.

At block 6010, optionally, the first portion of the data corresponds toa first privacy level. In some embodiments, different portions of thereceived data may correspond to different privacy levels or differentprivacy settings. For example, one portion of the data may be determinedto be less private and less sensitive, while another portion of the datamay be determined to be more private and more sensitive, while yetanother portion of the data may be determined to be most private andmost sensitive. In some embodiments, portions of the received data maybe defined or determined in accordance with a privacy or sensitivitylevel of the data. Dividing data into portions according to privacylevels may allow users to choose a privacy setting, thereby allowingusers to choose the privacy/sensitivity level of the data that they wishfor a device to display. This may be useful in allowing users tocustomize use of a device for different situations and settings, such asallowing display of more sensitive information when a user is home, andsuppressing display of more sensitive information when a user is inpublic and the display of his device may be viewed by others.

In the example depicted in FIG. 59A, the first portion of the receiveddata displayed by complication 5912 a may correspond to a first privacylevel, which in some embodiments corresponds to least sensitive data.For example, device 5900 may have received various pieces of informationabout an upcoming calendar event, and may have divided the informationinto portions. One portion of the data may relate to the time of theupcoming event, and this portion may be considered least sensitive.Another portion of the data may relate to the name of the upcomingevent, and this information may be considered more sensitive. Yetanother portion of the data may relate to the name of invitees orparticipants in the upcoming event, and this information may beconsidered most sensitive. In the example depicted in FIG. 59A, device5900 is in a first density state that corresponds to a first privacystate, and, accordingly, only the information corresponding to theportion of the data corresponding to the least sensitive data isdisplayed; that is, the time of the upcoming calendar event is displayedin complication 5912 a, but the name of the upcoming event andparticipants/invitees to the upcoming event are suppressed from display.

At block 6012, optionally, the first information is displayed in a firstfont size. In some embodiments, the manner in which informationcorresponding to one portion of received data is displayed may bedistinguished from the manner in which information corresponding toanother portion of the received data is displayed. In some embodiments,the manner of display may be distinguished by different display“densities,” which may correspond to different density settings of adevice. In some embodiments, density settings may correspond todisplaying a different amount of information and/or a different numberof user interface objects in the same area of a user interface, therebydefining more and less dense user interfaces. In some embodiments, oneportion of data displayed in a first density state may be displayed in afirst manner, while another portion of information displayed in a seconddensity state may be displayed in a second manner. In some embodiments,one portion of information displayed in a first density state may bedisplayed in a first size, while another portion of informationdisplayed in a second density state may be displayed in a second size.In some embodiments, information corresponding to more sensitive datamay be displayed in a smaller size, making it more difficult foronlookers to observe the information, while information corresponding toless sensitive information may be displayed in a larger size, making iteasier for a user to observe the information. Font size chosen fordisplay, in some embodiments, may thus correspond inversely to thesensitivity of data.

In some embodiments, information corresponding to different portions ofdata may be distinguished by different font size settings, with eachfont size setting corresponding to one or more than one font size. Forexample, a larger font size setting may include font sizes of size 12and 14, while a smaller font size setting may include font sizes of size10 and 12.

In the depicted example of FIG. 59A, as explained above, device 5900 maybe in a first density setting corresponding to a lowest density; and thefirst portion of the received data displayed by complication 5912 a maycorrespond to a first privacy level, which in some embodimentscorresponds to least sensitive data. In the depicted example, theinformation displayed corresponding to the first information may bedisplayed in a first font size or in a first font size setting.

At block 6014, optionally, the first information comprises a single lineof text. As described above, information presented in accordance withdifferent density settings may be visually distinguished. Furthermore,information presented as part of a higher-density setting may beconfigured to present a greater amount of information per display areaon a display. In some embodiments, in order to present more informationon the same area of a display (and the same area of a user interface),in addition to smaller font sizes being used, information may bepresented with different numbers of lines of text. In some embodiments,when different font sizes are used for information corresponding todifferent density settings, using different numbers of lines of text maybe facilitated by the different font sizes, such that more lines of textin a smaller font size may fit in the same vertical space as fewer linesof text in a larger font size.

In some embodiments, information corresponding to a lower privacysetting and a less dense density state may be displayed in a larger fontsize and may comprise a single line of text. In some embodiments,information corresponding to a higher privacy setting and a denserdensity state may be displayed in a smaller font size and may comprisemore than one line of text (or a greater number of lines of text thanthe information corresponding to a less dense density setting).

In the depicted example of FIG. 59A, as explained above, device 5900 maybe in a first density setting corresponding to a lowest density; and thefirst portion of the received data displayed by complication 5912 a maycorrespond to a first privacy level, which in some embodimentscorresponds to least sensitive data. In some embodiments, theinformation displayed corresponding to the first information may bedisplayed in a first font size or in a first font size setting. In thedepicted example, the information displayed corresponding to the firstinformation comprises a single line of text (e.g., the text “11:30” incomplication 5912 a does not have any other lines of text above or belowit).

At block 6016, optionally, the first information does not include icons,images, glyphs, or logos. In some embodiments, information relating toreceived data may be presented without the use, or with minimal use, oficons, images, glyphs, logos, or non-standard symbols. In someembodiments, information may be presented primarily or exclusively byway of text and numerals. In some embodiments, presenting informationprimarily or exclusively by text and numerals may include the limiteduse of standard typographic symbols, such as punctuation. In someembodiments, standard symbols may include widely used typographicalsymbols that may not be considered punctuation, such as the degreesymbol “°” used in complication 5914 a in FIG. 59A. In some embodiments,minimizing or avoiding use of non-standard symbols, icons, images,glyphs, or logos may aid users who wish for information to be displayedin typographic form, so that the user does not have to learn the meaningof custom symbols. Exclusively or primarily presenting typographicinformation may shorten a learning curve for a device and allow users tomore intuitively grasp a user interface, including the meaning of userinterface objects that they have not seen before.

In the depicted example of FIG. 59A, the first information presented incomplication 5912 a makes use only of numerals and punctuation, whilethe information presented in the other complications 5910 a, 5914 a, and5916 a makes use only of letters, numerals, punctuation, and thestandard typographical symbol “s”. None of the complications in FIG. 59Ainclude icons, images, glyphs, logos, or non-standard symbols.

At block 6018, optionally, the device receives data relating to a secondsubject matter. The second subject matter may be any subject matter,including any subject matter of the types described above with referenceto block 6004. In some embodiments, the second subject matter isdifferent from the first subject matter, and the data received by thedevice relating to the second subject matter may be associated with adifferent program or application than the information relating to thefirst subject matter.

At block 6020, optionally, the device displays, in a secondpredetermined portion of the user interface, third information relatingto a first portion of the data relating to the second subject matter.

In some embodiments, the second data received by the device may bedivided into portions in any of the manners described above withreference to block 6006. In some embodiments, a first portion of thedata relating to the second subject matter may correspond to a sameprivacy setting and/or a same density setting as the first portion ofthe data relating to the first subject matter. For example, in someembodiments, for each application or subject matter or data source forwhich data is received, the device may assign a portion of the data topredetermined privacy settings, such that portions of data relating todifferent subject matters may have corresponding privacy levels orsensitivity levels. In some embodiments, when a device is in a firstprivacy state and/or a first density state, information corresponding toportions of data associated with the same privacy level or sensitivitylevel may simultaneously be displayed.

In some embodiments, a user interface may be configured such thatvarious platters (e.g., predefined areas of the user interface) maydisplay information relating to respective subject matters. In someembodiments, predetermined portions of each platter may be configured todisplay information associated with a predetermined privacy orsensitivity level. For example, in some embodiments, platters may beportions of a user interface that are arranged as rows on the userinterface. In the example depicted in FIG. 59A, four platters containcomplications 5910 a-5914 a, respectively, which are arranged as rows oninterface 5950, stacked atop one another.

In the depicted example of FIG. 59A, device 5900 receives, among otherinformation, information from a weather application. The subject matterof the information received from the weather application is weatherdata, records, forecasts, and the like. In the depicted example, a firstportion of the weather data comprises information about a time of aforecasted weather temperature, which is 72°. In the depicted example,complication 5914 a displays the text “72°” in accordance with the firstportion of the received data. In the depicted example, complication 5914a is displayed in a different predetermined platter than complication5912 a.

At block 6022, optionally, device 5900 displays a first editinginterface for editing first display settings corresponding to the firstinformation and third displayed information, wherein the thirdinformation corresponds to a different subject matter than the firstsubject matter. In some embodiments, the third information isinformation displayed as part of a complication in a different platterfrom the first information displayed as part of a complication in afirst platter. In some embodiments, the third information may be thesame as the second information discussed above with reference to FIG.6020.

It should be noted that the editing interfaces and methods describedbelow may be freely combined with and modified by any of the editinginterfaces discussed above in this application in the “EditingContext-Specific User Interfaces” section of this disclosure orelsewhere.

In some embodiments, an editing interface may take the form of a clockface, or of a typographic modular interface, such that a user may editdisplay settings of a clock face or typographic modular face while beingprovided with a preview of what the edited interface will look like. Insome embodiments, an editing interface may be a different interface froman interface that displays information as discussed above with referenceto blocks 6007-6020. In some embodiments, an editing interface may beany interface allowing a user to modify one or more display settings ofan interface, including display settings of the editing interface ordisplay settings of any of the interfaces discussed above with referenceto blocks 6007-6020. In some embodiments, an editing interface mayinclude more than one user interface screen.

In some embodiments, an editing interface may be caused to be displayedwhen a device detects a touch contact whose characteristic intensity isabove an intensity threshold.

In the depicted example, device 5900 detects touch contact 5918 in FIG.59A. In some embodiments, device 5900 determines, via pressure-sensitivedisplay 5902, whether a characteristic intensity of touch contact 5918exceeds an intensity threshold. In accordance with the determinationthat a characteristic intensity of touch contact 5918 exceeds anintensity threshold, device 5900 causes interface screen 5960 in FIG.59B to be displayed. In the depicted example, interface screen 5960 isan editing interface screen that is identical to interface screen 5950with the exception of the presence of paging affordances 5919. In someembodiments, interface screen 5960 is an editing interface screen forediting one or more color settings and/or one or more density/privacysettings of device 5900, the color settings and/or density settingscorresponding to the first displayed information (e.g., complication5912 a in FIG. 59B) and third displayed information (e.g., any otherdisplayed complication, such as complication 5914 a in FIG. 59B).

In FIG. 60B, block 6002 is continued, such that method 6000 is furtherperformed at an electronic device having a display, a battery, and oneor more processors.

Block 6024 optionally follows from block 6022. At block 6024,optionally, blocks 6026-6052 (some of which are optional, and some ofwhich are depicted in FIG. 60C) are performed while displaying the firstediting interface. In the depicted example, blocks 6026-6052 may beperformed while displaying editing interface screen 5960 or a relatedinterface screen that is further a part of the same editing interface asediting interface screen 5960, as will be explained in further detailbelow.

At block 6026, the device detects a first rotation of the rotatableinput mechanism. In some embodiments, a first rotation of the rotatableinput mechanism may comprise one or more rotations in one or moredirections, having one or more speeds, having one or more durations, andhaving one or more spacings relative to one another. In someembodiments, a first rotation of the rotatable input mechanism maycomprise a single rotation of a rotatable input mechanism in apredefined rotational direction. In the example depicted in FIG. 59B,device 5900 detects user input 5920, which is a rotation of rotatableinput mechanism 5904.

At block 6028, in response to detecting the first rotation of therotatable input mechanism, the device supplements the first informationwith second information relating to a second portion of the receiveddata.

In some embodiments, a first rotation of the rotatable input mechanismmay be predetermined to be registered by the device as a command tochange a density/privacy setting of the device. In some embodiments,when the device is in an edit state or an edit interface, and the devicedetects a rotation of the rotatable input mechanism, the device may edita density/privacy state by cycling through two or more availableprivacy/density settings; for example, a device may change from a firstprivacy/density setting to a second, then a second to a third, then athird back to a first, each change coming in accordance with the devicedetecting rotation of the rotatable input mechanism of greater than apredefined threshold rotation angle and/or speed. In this way, a usermay twist a rotatable input mechanism to cycle through available densitysettings. Rotating a rotatable input mechanism in substantially oppositedirections may cause cycling through available density/privacy states inan opposite direction, such as from a first to a third, a third to asecond, and then a second to a first.

In some embodiments, when a device changes from a first, lower densitystate to a second, higher density state (e.g., less dense to denser),displayed information such as user interface objects or complicationsmay be supplemented with additional information. In some embodiments,supplemental information displayed by a previously displayedcomplication may include information relating to a portion of theunderlying data that has been determined to be of a higher sensitivitythan the portion of the data relating to the previously displayedinformation. Thus, in some embodiments, when a user changes aprivacy/density setting of a device, displayed embodiments may displayinformation relating to portions of underlying data having a highersensitivity. In some embodiments, because the information relating toportions of underlying data having a higher sensitivity may be takenfrom the same underlying data, the second displayed information may thusconcern the same subject matter as the first displayed information.

In the depicted example of FIG. 59C, in response to detecting user input5920 in FIG. 59B, device 5900 supplements each of the four displayedcomplications with additional information, the additional informationrelating to respective second portions of the same underlying data andsubject matter. In FIG. 59C, the complications are all displayed in asecond density state (and are accordingly denoted by reference numerals5910 b-5916 b) that is more dense than the density state of the samecomplications in FIG. 59B (as denoted by reference numerals 5910 a-5916a). In the particular example of the second platter of four (from thetop) in interface screen 5970 in FIG. 59C, complication 5912 b isdisplayed in a second density state, and has accordingly beensupplemented with second information relating to a second portion of theunderlying data corresponding to the upcoming calendar event. The secondinformation displayed in complication 5912 b (the text “Design Meeting”)is information relating to the name of the upcoming calendar event.

At block 6030, optionally, supplementing the first information withsecond information comprises displaying the second information in thefirst predetermined portion of the user interface. As described abovewith reference to block 6020, a user interface may be configured suchthat various platters (e.g., predefined areas of the user interface) maydisplay information relating to respective subject matters. In someembodiments, predetermined portions of each platter may be configured todisplay information associated with a predetermined privacy orsensitivity level. For example, in some embodiments, less sensitiveinformation may be displayed on the left side of a platter, while moresensitive information may be displayed on the right side of a platter.(This arrangement may be advantageous because onlookers may naturallystart reading from the left side, and may only have time to observe lesssensitive information if they are only observing the device for a shorttime.) In some embodiments, different pieces of information incomplications may be divided into separate sections in the complication(such as the way in which the text “11:30” and the text “Design Meeting”are separated in complication 5912 b in FIG. 59C). In some embodiments,separate sections in a complication may be justified to one side, havinga predefined spacing from one another (such as the way in which the text“Design Meeting” is the same distance from the text “11:30” incomplication 5912 b in FIG. 59B as the text “Cupertino Partly Cloudy” isfrom the text “72°” in complication 5914 b). In some embodiments,separate sections in a complication may be arranged into fixed columns,such that information relating to the same density/privacy setting maybe displayed in a cohesive vertical column.

In the displayed example of FIG. 59C, the second information in the formof the text “Design Meeting” is displayed in the same platter, as partof the same complication, as the first information in the form of thetext “11:30.”

At block 6032, optionally, supplementing the first information withsecond information comprises maintaining display of the firstinformation at a position of the display at which it was displayedbefore detection of the rotatable input mechanism. In some embodiments,rather than replacing, displacing, or otherwise disturbing informationalready displayed in a first privacy/density setting, informationdisplayed in a second privacy/density setting may be displayed inaddition to information that was already displayed when a device was ina first privacy/density setting. In some embodiments, information thatwas already displayed when a device was in a first privacy/densitysetting may be maintained in the same position on a display and/or inthe same position on a user interface when the device is set to a secondprivacy/density setting. In the depicted example of interface 5970 inFIG. 59C, when device 5900 is set to a second privacy/density settingand the complications each enter a second density state, the informationthat was originally displayed by complications 5910 a-5916 b in FIG. 59Bis not displaced, moved, occluded, or replaced in complications 5910b-5916 b in FIG. 59C, but is rather maintained at the same position onthe displayed interface and at the same position on display 5902.

At block 6034, optionally, the second portion of the data corresponds toa second privacy level. As described above with reference to block 6010,different portions of the received data may correspond to differentprivacy levels or different privacy settings. As the first informationdisplayed, as explained above with reference to block 6010, maycorrespond to a first privacy level, the second information maycorrespond to a second privacy level. In some embodiments, the secondprivacy level may correspond to the display of more sensitiveinformation that the first privacy level, while in some embodiments thesecond privacy level may correspond to the display of less sensitiveinformation that the first privacy level.

In the example depicted in FIG. 59C, the second portion of the receiveddata displayed by complication 5912 b may correspond to a second privacylevel, which in some embodiments corresponds to more sensitive data thanthe data to which the first privacy level corresponds. For example,device 5900 may have received various pieces of information about anupcoming calendar event, and may have divided the information intoportions. One portion of the data may relate to the time of the upcomingevent, and this portion may be considered least sensitive. Anotherportion of the data may relate to the name of the upcoming event, andthis information may be considered more sensitive. Yet another portionof the data may relate to the name of invitees or participants in theupcoming event, and this information may be considered most sensitive.In the example depicted in FIG. 59C, device 5900 is in a second densitystate that corresponds to a second privacy state, and, accordingly,information corresponding to the portion of the data corresponding tothe more sensitive data is displayed in addition to informationcorresponding to the least sensitive portion of the data; that is, inaddition to the time of the upcoming calendar event, the name of theupcoming calendar event is also displayed is displayed in complication5912 b.

At block 6036, optionally, the second information is displayed in asecond font size smaller than the first font size. As described abovewith reference to block 6012, in some embodiments, informationcorresponding to different privacy or sensitivity levels, or informationcorresponding to different density states, may be displayed in differentfont sizes or different font size settings. In some embodiments, lesssensitive information corresponding to a lower density setting may bedisplayed in a larger font size setting, while more sensitiveinformation corresponding to a higher density setting may be displayedin a smaller font size setting. In the depicted example of FIG. 59C, thesecond information, in the form of the text “Design Meeting” incomplication 5912 b, is displayed in a smaller font size than the fontsize in which the first information, in the form of the text “11:30” incomplication 5912 b, is displayed.

At block 6038, optionally, the second information comprises two or morelines of text. As explained above with reference to block 6014, in someembodiments, information corresponding to different privacy orsensitivity levels, or information corresponding to different densitystates, may be displayed in differing numbers of lines of text, whichmay in some embodiments be facilitated by their being displayed indiffering font size settings. In some embodiments, less sensitiveinformation corresponding to a lower density setting may be displayed bya single line of text, while more sensitive information corresponding toa higher density setting may be displayed by more than one line of text(or by more lines of text than are used for the less sensitiveinformation). In the depicted example of FIG. 59C, the secondinformation, in the form of the text “Design Meeting” in complication5912 b, is displayed by two lines of text.

At block 6040, optionally, the second information does not includeicons, images, glyphs, or logos. As described above with reference toblock 6016, displayed information may be presented primarily orexclusively in the form of letters, numerals, and standard typographicalsymbols. In the depicted example of FIG. 59C, the second informationpresented in complication 5912 b makes use only of letters (“DesignMeeting”), while the second information presented in the othercomplications 5910 b, 5914 b, and 5916 b also makes use only of letters,numerals, punctuation, and the standard typographical symbol “+”. Noneof the complications in FIG. 59C include icons, images, glyphs, logos,or non-standard symbols.

In FIG. 60C, block 6002 is continued, such that method 6000 is furtherperformed at an electronic device having a display, a battery, and oneor more processors. In FIG. 60C, block 6024 is, optionally, continued,such that blocks 6042-6052 are, optionally, performed while displayingthe first editing interface. In the depicted example, blocks 6042-6052may be performed while displaying editing interface screen 5960 or arelated interface screen that is further a part of the same editinginterface as editing interface screen 5960, as will be explained infurther detail below.

At block 6042, optionally, the device detects a first touch input at alocation corresponding to the first information. The touch inputdetected may be a single-touch input, a multi touch input, a single-tapinput, and/or a multi-tap input detected by touch- and/or pressuresensitive elements in any touch- and/or pressure-sensitive surface,including a touchscreen. In some embodiments, a device may detect atouch contact at a location that corresponds to the first information.In some embodiments, the touch input may be detected on a touchscreen,such as display 5902. In some embodiments, the touch input may bedetected at a location at which the first information is displayed. Insome embodiments, the touch input may be detected at a location of aplatter in which the first information is displayed, such that the touchcontact may be detected at a location corresponding to informationassociated with the first information, such as second or thirdinformation included in the same complication in the same platter as thefirst information.

In the depicted example of FIG. 59C, device 5900 detects user input5922, which is a tap input detected on display 5902 at a locationcorresponding to complication 5912 b in the second of four complicationplatters on interface screen 5970.

At block 6044, optionally, in response to detecting the first touchinput at the location corresponding to the first information, the devicehighlights the first information. In some embodiments, a touch inputdetected at a location corresponding to first information, detectedwhile a device is in an editing state, may be predetermined to cause thedevice to select the first information for editing of one or moredisplay settings. In some embodiments, when a user taps on a displayedcomplication when a device is in an editing state, the complication maybe selected for editing of one or more display settings, such as a colorsetting. In some embodiments, once selected, a user may use one or moreinputs to modify a color setting of the selected complication and/or theselected displayed information.

In some embodiments, highlighting first information may includedisplaying the first information in accordance with any distinct visualappearance suitable to distinguish it from other displayed informationin an interface, or suitable to distinguish it from a previous visualappearance of the same information. In some embodiments, highlightingmay be achieved by changing a display size, display color, backgroundcolor, outline setting, underline setting, italic setting, bold setting,font size setting, font setting, outline setting, animation style, orany other suitable aspect of the visual appearance of displayedinformation. In the depicted embodiment in FIG. 59D, in response todetecting input 5922 in FIG. 59C, device 5900 highlights complication5912 b by displaying the text of complication 5912 b at a larger sizeand in a bolded font as compared to the appearance of the othercomplications 5910 b, 5914 b, and 5916 b in editing interface screen5980 in FIG. 59D (and as compared to the previous appearance ofcomplication 5912 b in editing interface screen 5970 in FIG. 59C).

At block 6046, optionally, while the first information is highlighted,the device detects a second rotation of the rotatable input mechanism.In some embodiments, a second rotation of the rotatable input mechanismmay comprise one or more rotations in one or more directions, having oneor more speeds, having one or more durations, and having one or morespacings relative to one another. In some embodiments, a second rotationof the rotatable input mechanism may comprise a single rotation of arotatable input mechanism in a predefined rotational direction. In theexample depicted in FIG. 59D, while device 5900 is displaying theinformation in complication 5912 b in a highlighted (bold and largerfont size) appearance, device 5900 detects user input 5924, which is arotation of rotatable input mechanism 5904.

At block 6048, optionally, in response to detecting the second rotationof the rotatable input mechanism, the device edits a first color settingcorresponding to the first information. In some embodiments, colorsettings may be modified by a user using an edit interface such as theone depicted in part by editing interface screens 5960, 5970, and 5980in FIGS. 59B, 59C, and 59D, respectively. In some embodiments, after auser has selected certain information, such as a one or morecomplications or platters, for editing, the user may then execute arotational input through a rotatable input mechanism to edit a colorsetting of the selected information. In some embodiments, there may be apredefined selection of color settings each corresponding to a color,series of colors, pattern of colors, or animation by which a colorsetting changes in time. In some embodiments, one or more of the colorsettings are a gradient color setting or a pattern color setting thatrenders the complication text (in the first or second density state) asa continuous color gradient or pattern across the different letters andnumbers in the complication. The predefined color settings may bearranged into an ordered progression. When the user selects acomplication for editing and rotates the rotational input mechanism, thesetting may be modified by cycling or scrolling through the orderedprogression to a next or previous color setting in accordance with adirection of the rotation of the input. The color setting may be changedin response to the rotatable input mechanism being rotated at leastthrough a predefined minimum rotation angle, such that one longcontinuous rotation may cause the device to progress sequentiallythrough a series of color settings. In some embodiments, the orderedprogression may loop around from the last setting to the first.

In the depicted example of FIG. 59D, a color setting of complication5912 b may be modified in accordance with user input 5924, although thechange to a color setting is not depicted by the black-and-white figure.

At block 6050, optionally, in response to detecting the second rotationof the rotatable input mechanism, the device maintains a second colorsetting corresponding to the third information. As explained above withreference to block 6022, the third information, in some embodiments, isinformation displayed as part of a complication in a different platterfrom the first information displayed as part of a complication in afirst platter. Thus, in some embodiments, when a color setting of oneplatter, complication, or other displayed information is edited, thecolor setting of another platter, complication, or other displayedinformation may be maintained and not changed. In some embodiments,users may wish to be able to individually customize the color settingsof complications on an interface, which may help users to assignmeaningful color-complication relationships in accordance with theirchosen arrangement of complications.

Block 6052 optionally follows from block 6048. At block 6052,optionally, in response to detecting the second rotation of therotatable input mechanism, the device edits a second color settingcorresponding to the third information. As explained above withreference to block 6022, the third information, in some embodiments, isinformation displayed as part of a complication in a different platterfrom the first information displayed as part of a complication in afirst platter. Thus, in some embodiments, when a color setting of oneplatter, complication, or other displayed information is edited, thecolor setting of another platter, complication, or other displayedinformation may be edited in accordance with the same input that causedthe editing of the first platter, complication, or other displayedinformation.

In some embodiments, a user may edit a color setting of more than one ofthe complications/platters, or of all of the complications/platters, atthe same time. For example, color themes may be predetermined and savedon the device (or available to the device by network communication),such that a user may select a single theme that assigns a color settingto more than one or all of the complications/platters. In someembodiments, themes may assign a predetermined color setting to apredetermined platter. In some embodiments, themes may assign apredetermined color setting to a predetermined type of complication,regardless of the platter in which it appears. In some embodiments, atheme may be a gradient theme or a pattern theme that renders more thanone of the complications/platters, or all of the complications/platters,as a continuous gradient or a continuous pattern across the letters andnumbers in the multiple complications/platters. In some embodiments,selecting a predefined color setting scheme or theme may be advantageousbecause it may allow a user to assign color settings to complicationssuch that adjacent colors are adequately contrasting, making distinctionbetween complications easier. In some embodiments, themes that assignpredefined color settings to predefined complications or types ofcomplications (rather than to platters) may be advantageous because theymay help a user to quickly identify a complication or complication typebased on its color.

In FIG. 60D, block 6002 is continued, such that method 6000 is furtherperformed at an electronic device having a display, a battery, and oneor more processors.

Block 6054 optionally follows from blocks 6024-6052. At block 6054,while displaying the first editing interface, the device detects ahorizontal swipe gesture. In some embodiments, the horizontal swipegesture may be detected at any location on a touch-sensitive surface orat any location on a touch-sensitive surface corresponding to the firstediting interface. In this way, the horizontal swipe gesture may besaid, in some embodiments, to be location independent. In the depictedexample of FIG. 59D, device 5900 detects user input 5926, which is aleftward swipe gesture applied to the touch-sensitive screen 5902.

At block 6056, optionally, in response to detecting the horizontal swipegesture, the device displays a second editing interface for editingsecond display settings corresponding to the first information and thethird information. In some embodiments, the second editing interface maybe an interface for editing a different display setting or a differentdisplay characteristic of the same underlying user interface. In someembodiments, the second editing interface may be a second page amongseveral editing interface pages that are accessible by paging from sideto side. In some embodiments, a user may swipe from side to side tonavigate between one editing interface or editing page and other editinginterfaces or editing pages, for example, by swiping to the left toaccess a page to the right, or by swiping to the right to access a pageto the left. In some embodiments, editing interface pages which may bepaged through by a user may each correspond to editing a differentdisplay setting; a page may be configured to edit a color setting, afont setting, a text size setting, a text style (e.g., underline, bold,italics, etc.), a location setting (e.g., the location at whichinformation is displayed), a privacy setting, a density setting, and/ora complication identity setting (e.g., the underlying data orinformation which is displayed in a given slot, location, or platter).In some embodiments, editing interface pages may be configured to editmore than one display setting in accordance with predefined user inputs.

In the depicted example of FIGS. 59D and 59F, editing interface screen5980 in FIG. 59D may, in some embodiments, be considered a first editinginterface, while editing interface screen 5990 in FIG. 59E may, in someembodiments, be considered a second, distinct editing interface. In thedepicted example, editing interface 5980 in FIG. 59D is configured toallow a user to edit color settings (as explained above with referenceto blocks 6042-6052) by selecting a platter for editing and thenrotating rotatable input mechanism 5904. In the depicted example,editing interface 5990 in FIG. 59E is configured to allow a user to editcomplication identity settings. In a similar manner as described abovewith reference to editing color settings in blocks 6042-6052, a usermay, in some embodiments, tap a platter on display 5902 to select theplatter for editing, and execute one or more rotational inputs ofrotatable input mechanism 5904 in order to cycle through availablecomplications that may be displayed in each platter (including selectingto display no complication in a platter). In some embodiments, a usermay edit the complication identity setting of more than one platter atonce, for example, by selecting more than one platter for editing, or byselecting a predefined or curated theme or scheme of complications to bedisplayed in predefined platters. In some embodiments, one or more ofthe first and second editing interface may be configured to allow a userto edit a density setting of device 5900 (as described above withreference to blocks 6026-6040) by rotating rotatable input mechanism5904 when no complication or platter is selected for editing.

In FIG. 60E, block 6002 is continued, such that method 6000 is furtherperformed at an electronic device having a display, a battery, and oneor more processors.

Block 6058 optionally follows from blocks 6024-6052. At block 6058,optionally, the device displays a third editing interface for editingthird display settings corresponding to the first information and thirddisplayed information, wherein the third information corresponds to adifferent subject matter than the first subject matter. In someembodiments, the third editing interface may share some or all of thecharacteristics of the first and/or second editing interfaces describedabove with reference to blocks 6022 and 6056, respectively. In someembodiments, the third editing interface may be the same interface asthe second editing interface described above with reference to block6056, including that it may be accessed by executing a swipe gesturewhile displaying the first editing interface, as described above withreference to blocks 6054-6056. In the depicted example of FIG. 59E,editing interface screen 5990 is displayed by device 5900.

At block 6060, optionally, blocks 6062-6070 are optionally performedwhile displaying the third editing interface. In the depicted example ofFIGS. 59E-59F, blocks 6062-6070 may be performed while displayingediting interface screen 5990 or a related interface screen that isfurther a part of the same editing interface as editing interface screen5990, as will be explained in further detail below.

At block 6062, the device detects a second touch input at a locationcorresponding to the first information. The touch input detected may bea single-touch input, a multi touch input, a single-tap input, and/or amulti-tap input detected by touch- and/or pressure sensitive elements inany touch- and/or pressure-sensitive surface, including a touch-screen.In some embodiments, a device may detect a touch contact at a locationthat corresponds to the first information. In some embodiments, thetouch input may be detected on a touchscreen, such as display 5902. Insome embodiments, the touch input may be detected at a location at whichthe first information is displayed. In some embodiments, the touch inputmay be detected at a location of a platter in which the firstinformation is displayed, such that the touch contact may be detected ata location corresponding to information associated with the firstinformation, such as second or third information included in the samecomplication in the same platter as the first information.

At block 6064, optionally, in response to detecting the second touchinput at the location corresponding to the first information, the devicehighlights the first information. In some embodiments, the device mayhighlight the first information in any of the manners described abovewith reference to block 6044.

In some embodiments, rather than detecting a touch input while the thirdediting interface is displayed and responsively highlighting acomplication or a platter, a complication or platter may already behighlighted when the third editing interface is accessed. This mayoccur, in some embodiments, when a user has already selected aplatter/complication for editing in a previous editing interface, andpages to a new editing interface. In some embodiments, paging betweenediting interfaces may cause previously selected platters/complicationsto no longer be highlighted, while, in some embodiments, paging betweenediting interfaces may cause previously selected platters/complicationsto remain selected for editing and remain highlighted upon displayingthe new editing interface.

In the depicted example of FIG. 59E, complication 5912 b is selected forediting and accordingly highlighted by being displayed in a bold fontand at an increased font size as compared to the other complications5910 b, 5914 b, and 5916 b in interface 5990. In the depicted example,complication 5912 b was highlighted in accordance with having beenpreviously selected for editing by touch input 5922 in FIG. 59C, ratherthan in the manner described above by blocks 6062 and 6064.

At block 6066, optionally, while the first information is highlighted,the device detects a second rotation of the rotatable input mechanism.In some embodiments, a second rotation of the rotatable input mechanismmay comprise one or more rotations in one or more directions, having oneor more speeds, having one or more durations, and having one or morespacings relative to one another. In some embodiments, a second rotationof the rotatable input mechanism may comprise a single rotation of arotatable input mechanism in a predefined rotational direction. In theexample depicted in FIG. 59E, while device 5900 is displaying theinformation in complication 5912 b in a highlighted (bold and largerfont size) appearance, device 5900 detects user input 5928, which is arotation of rotatable input mechanism 5904.

At block 6068, optionally, in response to detecting the third rotationof the rotatable input mechanism, the device replaces the firstinformation with fourth information corresponding to a different subjectmatter than the first subject matter. In some embodiments, complicationidentity settings may be edited by a user in an analogous manner to theway in which color settings may be edited, as described above withreference to block 6048. Just as a user may cycle through color settingsfor one or more complications by selecting a complication for editingand rotating the rotatable input mechanism in some editing interfaces, auser may similarly cycle through complication identity settings for oneor more platters by selecting a complication/platter for editing androtating the rotatable input mechanism in some interfaces. Rather thanediting a color setting, however, (or, in some embodiments, in additionto editing a color setting), the device may cycle through differentcomplications by replacing the complication displayed in a selectedplatter with one or more next or previous available complications inaccordance with a magnitude and/or speed of a user's rotation. In someembodiments, a user may select from any available complication to bedisplayed in the selected platter, or may select an option fordisplaying no complication in the selected platter.

In the depicted example of FIG. 59F, in response to detecting user input5928 in FIG. 59E, device 5900 replaces complication 5912 b in FIG. 59Ewith complication 5930 b in FIG. 59F. In the depicted example,complication 5930 b is a stock-market complication which displaysinformation about the performance of the Standard & Poor's stock marketindex (e.g., a gain of 54.48 points). Note that complication 5930 b isdisplayed in a second density/privacy state, as are the othercomplications in FIG. 59F. Further note that complication 5930 b isdisplayed in a highlighted state with bolded font and font of a largersize than the other complications 5910 b, 5914 b, and 5916 b ininterface 5992, so as to signify that complication 5930 b and or itsassociated platter remain selected for editing.

At block 6070, optionally, in response to detecting the third rotationof the rotatable input mechanism, the device maintains display of thethird information. As explained above with reference to block 6022, thethird information, in some embodiments, is information displayed as partof a complication in a different platter from the first informationdisplayed as part of a complication in a first platter. Thus, in someembodiments, when a complication identity setting of one platter isedited, the complication identity setting of another platter may bemaintained and not changed. In the depicted example of FIG. 59F, whencomplication 5930 b replaces complication 5912 b from FIG. 59E, theother complications 5910 b, 5914 b, and 5916 b are maintained on display5902.

In some embodiments, when a complication identity setting of one platteris edited, the complication identity setting of another platter may beedited in accordance with the same input that caused the editing of thefirst platter. This may occur, in some embodiments, when a user selectsa predefined theme or scheme of related or otherwise curatedcomplications, each one being assigned to a predefined platter.

In FIG. 60F, block 6002 is continued, such that method 6000 is furtherperformed at an electronic device having a display, a battery, and oneor more processors. In FIG. 60C, block 6024 is, optionally, continuedfrom FIG. 60B, such that blocks 6072-6074 are, optionally, performedwhile displaying the first editing interface.

Block 6074 optionally follows from blocks 6028-6040. At block 6074, thedevice detects a fourth rotation of the rotatable input mechanism. Insome embodiments, a first rotation of the rotatable input mechanism maycomprise one or more rotations in one or more directions, having one ormore speeds, having one or more durations, and having one or morespacings relative to one another. In some embodiments, a first rotationof the rotatable input mechanism may comprise a single rotation of arotatable input mechanism in a predefined rotational direction.

At block 6076, optionally, in response to detecting the fourth rotationof the rotatable input mechanism, the device supplements the firstinformation and the second information with fourth information relatingto a third portion of the received data. In some embodiments, the fourthinformation may correspond to a third portion of the same data used bythe device to present the first information and the second information.As described above with reference to block 6010, the receivedinformation may be divided into portions; in some embodiments, the thirdportion of the data may be determined to be even more private and evenmore sensitive than the first and second portions of the data. In someembodiments, the fourth information relating to the third portion of thereceived data may be presented when the device is set to a thirdprivacy/density state, such as by a user executing an additionalrotational input or a further rotational input in any of the mannersdescribed above with reference to blocks 6026-6040. That is, in someembodiments, a user may execute a first rotation to supplement thefirst, less sensitive information with the second, more sensitiveinformation; the user may then continue the rotation or execute anadditional rotation in the same direction to supplement the first andsecond information with the fourth, even more sensitive information. Insome embodiments, the even more sensitive information may be displayedin the same platter as the first and second information, simply furtherto the right. In some embodiments, the even more sensitive informationmay be displayed in an even smaller font size setting than the font sizesetting corresponding to the second information. In some embodiments,the even more sensitive information may include even more lines of textthan the second information. In some embodiments, the even moresensitive information may be presented without the use (or with limiteduse) of icons, images, glyphs, or logos.

It should be understood that the particular order in which theoperations in FIG. 60 have been described is merely exemplary and is notintended to indicate that the described order is the only order in whichthe operations could be performed. One of ordinary skill in the artwould recognize various ways to reorder the operations described herein.

Note that details of the processes described above with respect tomethod 6000 (e.g., FIG. 60) are also applicable in an analogous mannerto the methods described elsewhere in this application. For example,other methods described in this application may include one or more ofthe characteristics of method 6000. For example, the devices, hardwareelements, inputs, interfaces, modes of operation, faces, timeindicators, and complications described above with respect to method6000 may share one or more of the characteristics of the devices,hardware elements, inputs, interfaces, modes of operation, faces, timeindicators, and complications described elsewhere in this applicationwith respect to other methods. Moreover, the techniques described abovewith respect to method 6000 may be used in combination with any of theinterfaces, faces, or complications described elsewhere in thisapplication. For brevity, these details are not repeated elsewhere inthis application.

In accordance with some embodiments, FIG. 61 shows an exemplaryfunctional block diagram of an electronic device 6100 configured inaccordance with the principles of the various described embodiments. Inaccordance with some embodiments, the functional blocks of electronicdevice 6100 are configured to perform the techniques described above.The functional blocks of the device 6100 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 61 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

As shown in FIG. 61, electronic device 6100 includes display unit 6102configured to display a graphic user interface such as a typographicmodular interface and/or an editing interface, and rotatable inputmechanism unit 6104 configured to receive rotational inputs. Optionally,device 6100 also includes a touch-sensitive surface unit 6106 configuredto receive contacts. Device 6100 further includes processing unit 6108coupled to display unit 6102, rotatable input mechanism unit 6104, and,optionally, touch-sensitive surface unit 6106. Processing unit 6108contains receiving unit 6110, display enabling unit 6112, detecting unit6114 and supplementing unit 6116. Optionally, processing unit 6108further includes highlighting unit 6118, editing unit 6120, maintainingunit 6122, and replacing unit 6124.

Processing unit 6112 is configured to: receive (e.g., with receivingunit 6110) data relating to a first subject matter; enable display(e.g., with display enabling unit 6112) on the display unit 6102 offirst information relating to a first portion of the received data;detect (e.g., with detecting unit 6114) a first rotation of therotatable input mechanism unit 6104; and, in response to detecting thefirst rotation of the rotatable input mechanism unit 6104, supplement(e.g., with supplementing unit 6116) the first information with secondinformation relating to a second portion of the received data.

In some embodiments, enabling display (e.g., with display enabling unit6112) on the display unit 6102 of first information comprises enablingdisplay on the display unit 6102 of the first information in a firstpredetermined portion of a user interface.

In some embodiments, supplementing the first information with secondinformation comprises enabling display on the display unit 6102 of thesecond information in the first predetermined portion of the userinterface.

In some embodiments, wherein supplementing (e.g., with display enablingunit 6112) the first information with second information comprisesmaintaining display of the first information at a position of thedisplay unit 6102 at which it was displayed before detection of therotatable input mechanism unit 6104.

In some embodiments, processing unit 6108 is further configured to:receive (e.g., with receiving unit 6110) data relating to a secondsubject matter; enable display (e.g., with display enabling unit 6112)on the display unit 6102, in a second predetermined portion of the userinterface, of third information relating to a first portion of the datarelating to the second subject matter.

In some embodiments, the first portion of the data corresponds to afirst privacy level; and the second portion of the data corresponds to asecond privacy level.

In some embodiments, the first information is displayed on the displayunit 6102 in a first font size; and the second information is displayedon the display unit 6102 in a second font size smaller than the firstfont size.

In some embodiments, the first information comprises a single line oftext; the second information comprises two or more lines of text.

In some embodiments, processing unit 6108 is further configured to:enable display (e.g., with display enabling unit 6112) on the displayunit 6102 of a first editing interface for editing first displaysettings corresponding to the first information and the thirdinformation, while enabling display (e.g., with display enabling unit6112) on the display unit 6102 of the first editing interface: detect(e.g., with detecting unit 6114) a first touch input at a locationcorresponding to the first information; in response to detecting thefirst touch input at the location corresponding to the firstinformation, highlight (e.g., with highlighting unit 6118) the firstinformation; while the first information is highlighted, detect (e.g.,with detecting unit 6114) a second rotation of the rotatable inputmechanism unit 6104; and in response to detecting the second rotation ofthe rotatable input mechanism unit 6104, edit (e.g., with editing unit6120) a first color setting corresponding to the first information.

In some embodiments, processing unit 6108 is further configured to:while enabling display (e.g., with display enabling unit 6112) on thedisplay unit 6102 of the first editing interface: in response todetecting the second rotation of the rotatable input mechanism unit6104, maintain (e.g., with maintaining unit 6122) a second color settingcorresponding to the third information.

In some embodiments, processing unit 6108 is further configured to:while enabling display (e.g., with display enabling unit 6112) on thedisplay unit 6102 of the first editing interface: in response todetecting the second rotation of the rotatable input mechanism unit6104, edit (e.g., with editing unit 6120) a second color settingcorresponding to the third information.

In some embodiments, processing unit 6108 is further configured to:while enabling display (e.g., with display enabling unit 6112) on thedisplay unit 6102 of the first editing interface, detect (e.g., withdetecting unit 6114) a horizontal swipe gesture; and in response todetecting the horizontal swipe gesture, enable display (e.g., withdisplay enabling unit 6112) on the display unit 6102 of a second editinginterface for editing second display settings corresponding to the firstinformation and the third information.

In some embodiments, processing unit 6108 is further configured to:enable display (e.g., with display enabling unit 6112) on the displayunit 6102 of a third editing interface for editing third displaysettings corresponding to the first information and the thirdinformation; while enabling display (e.g., with display enabling unit6112) on the display unit 6102 of the third editing interface: detect(e.g., with detecting unit 6114) a second touch input at a locationcorresponding to the first information; in response to detecting thesecond touch input at the location corresponding to the firstinformation, highlight (e.g., with highlighting unit 6118) the firstinformation; while the first information is highlighted, detect (e.g.,with detecting unit 6114) a third rotation of the rotatable inputmechanism unit 6104; and in response to detecting the third rotation ofthe rotatable input mechanism unit 6104, replace (e.g., with replacingunit 6124) the first information with fourth information correspondingto a different subject matter than the first subject matter.

In some embodiments, processing unit 6108 is further configured to:while enabling display (e.g., with display enabling unit 6112) on thedisplay unit 6102 of the third editing interface: in response todetecting the third rotation of the rotatable input mechanism unit 6104,maintain (e.g., with maintaining unit 6122) display on the display unit6102 of the third information.

In some embodiments, processing unit 6108 is further configured to:detect a fourth rotation of the rotatable input mechanism unit 6104; inresponse to detecting the fourth rotation of the rotatable inputmechanism unit 6104, supplement the first information and the secondinformation with fourth information relating to a third portion of thereceived data.

In some embodiments, the first information and the second information donot include icons, images, glyphs, or logos.

The functional blocks of the device 6100 are, optionally, implemented byhardware, software, or a combination of hardware and software to carryout the principles of the various described examples. It is understoodby persons of skill in the art that the functional blocks described inFIG. 61 are, optionally, combined or separated into sub-blocks toimplement the principles of the various described examples. Therefore,the description herein optionally supports any possible combination orseparation or further definition of the functional blocks describedherein.

The operations described above with reference to FIGS. 60A-60F are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG.59. For example, receiving operation 6004, displaying operation 6006,detecting operation 6026, and supplementing operation 6028 may beimplemented by event sorter 170, event recognizer 180, and event handler190. Event monitor 171 in event sorter 170 detects a contact ontouch-sensitive display 112, and event dispatcher module 174 deliversthe event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface corresponds to apredefined event or sub event, such as activation of an affordance on auser interface. When a respective predefined event or sub-event isdetected, event recognizer 180 activates an event handler 190 associatedwith the detection of the event or sub-event. Event handler 190 mayutilize or call data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying figures, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe appended claims.

What is claimed is:
 1. An electronic device, comprising: a display; atouch-sensitive surface; one or more processors; a memory; and one ormore programs, wherein the one or more programs are stored in the memoryand configured to be executed by the one or more processors, the one ormore programs including instructions for: displaying a character userinterface object on the display, the character user interface objectcomprising representations of a first limb and a second limb, whereinthe character user interface object indicates a first time by:indicating a first hour with the first limb and a first minute with thesecond limb; and updating the character user interface object toindicate a second time, wherein the character user interface objectindicates the second time by: indicating a second hour with the secondlimb and a second minute with the first limb.
 2. The electronic deviceof claim 1, wherein updating the character user interface object toindicate a second time comprises an extension of the first limb and aretraction of the second limb.
 3. The electronic device of claim 1, theone or more programs further including instructions for: translating thecharacter user interface object on-screen towards a center of thedisplay.
 4. The electronic device of claim 3, wherein translating thecharacter user interface object comprises animating the character userinterface object to represent walking.
 5. The electronic device of claim1, the one or more programs further including instructions for: changinga visual aspect of the display to highlight the character user interfaceobject.
 6. The electronic device of claim 5, the one or more programsfurther including instructions for: animating the character userinterface object in response to being highlighted.
 7. The electronicdevice of claim 1, wherein the character user interface object furthercomprises a representation of a foot.
 8. The electronic device of claim7, the one or more programs further including instructions for:animating the foot to indicate passage of time.
 9. The electronic deviceof claim 1, the one or more programs further including instructions for:displaying on the display a numerical indication of a time value.
 10. Amethod, comprising: at an electronic device with a display and atouch-sensitive surface: displaying a character user interface object onthe display, the character user interface object comprisingrepresentations of a first limb and a second limb, wherein the characteruser interface object indicates a first time by: indicating a first hourwith the first limb and a first minute with the second limb; andupdating the character user interface object to indicate a second time,wherein the character user interface object indicates the second timeby: indicating a second hour with the second limb and a second minutewith the first limb.
 11. The method of claim 10, wherein updating thecharacter user interface object to indicate a second time comprises anextension of the first limb and a retraction of the second limb.
 12. Themethod of claim 10, further comprising: translating the character userinterface object on-screen towards a center of the display.
 13. Themethod of claim 12, wherein translating the character user interfaceobject comprises animating the character user interface object torepresent walking.
 14. The method of claim 10, further comprising:changing a visual aspect of the display to highlight the character userinterface object.
 15. The method of claim 14, further comprising:animating the character user interface object in response to beinghighlighted.
 16. The method of claim 10, wherein the character userinterface object further comprises a representation of a foot.
 17. Themethod of claim 16, further comprising: animating the foot to indicatepassage of time.
 18. The method of claim 10, further comprising:displaying on the display a numerical indication of a time value.
 19. Anon-transitory, non-signal computer readable storage medium storing oneor more programs for execution by one or more processors of anelectronic device with a display and a touch-sensitive surface, the oneor more programs including instructions for: displaying a character userinterface object on the display, the cha racter user interface objectcomprising representations of a first limb and a second limb, whereinthe character user interface object indicates a first time by:indicating a first hour with the first limb and a first minute with thesecond limb; and updating the character user interface object toindicate a second time, wherein the character user interface objectindicates the second time by: indicating a second hour with the secondlimb and a second minute with the first limb.
 20. The non-transitory,non-signal computer readable storage medium of claim 19, whereinupdating the character user interface object to indicate a second timecomprises an extension of the first limb and a retraction of the secondlimb.
 21. The non-transitory, non-signal computer readable storagemedium of claim 19, the one or more programs further includinginstructions for: translating the character user interface objecton-screen towards a center of the display.
 22. The non-transitory,non-signal computer readable storage medium of claim 21, whereintranslating the character user interface object comprises animating thecharacter user interface object to represent walking.
 23. Thenon-transitory, non-signal computer readable storage medium of claim 19,the one or more programs further including instructions for: changing avisual aspect of the display to highlight the character user interfaceobject.
 24. The non-transitory, non-signal computer readable storagemedium of claim 23, the one or more programs further includinginstructions for: animating the character user interface object inresponse to being highlighted.
 25. The non-transitory, non-signalcomputer readable storage medium of claim 19, wherein the character userinterface object further comprises a representation of a foot.
 26. Thenon-transitory, non-signal computer readable storage medium of claim 25,the one or more programs further including instructions for: animatingthe foot to indicate passage of time.
 27. The non-transitory, non-signalcomputer readable storage medium of claim 19, the one or more programsfurther including instructions for: displaying on the display anumerical indication of a time value.